Bug 39897 – freetype (all versions) with gcc33

• Status: RESOLVED WONTFIX
• Product: Gentoo Linux

[Description Dietrich Heise 2004-01-30 11:14:36 UTC]

all ebuilds need to be added by:

append-flags "-fno-strict-aliasing"

to compile right.

Reproducible: Always
Steps to Reproduce:

[Comment 1 Robin Johnson 2004-01-30 14:25:45 UTC]

could you provide some further justification (eg, upstream) for this?
I've never had any problems with freetype compiling at all.

[Comment 2 Dietrich Heise 2004-01-30 18:47:14 UTC]

read this:
http://www.freetype.org/pipermail/devel/2003-June/009452.html

[Comment 3 Luca Barbato 2004-01-31 17:32:16 UTC]

at most we should patch the makefiles to ensure the particular file are compiled in the right way OR let the upstream developers fix the code themselves.

Anyway gcc is still smart enough to discover when the strict aliasing rules are to be avoided...

[Comment 4 Dietrich Heise 2004-02-05 03:04:22 UTC]

Created attachment 24993 [details, diff]
ftdump.c.patchgcc33

patch freetype with with:

patch test/ftdump.c ftdump.c.patchgcc33

[Comment 5 Dietrich Heise 2004-02-05 03:41:24 UTC]

Created attachment 24995 [details, diff]
ftdump.c.patchgcc33

[Comment 6 Dietrich Heise 2004-02-05 03:42:12 UTC]

Created attachment 24996 [details]
freetype-1.3.1-r3.ebuild

[Comment 7 foser (RETIRED) 2004-08-08 02:56:33 UTC]

i added -fno-strict-aliasing to 2.1.9, although for another reason.

I see no reason to change this in all older versions as long as it doesn't break. Your report or the mail thread do not suggest that. What i do see is that disabling it is slower, that is not good.

[Comment 8 Dietrich Heise 2005-03-15 16:51:21 UTC]

seems to be gone with gcc-3.4.x