Summary: | app-text/texlive-core-2012-r1 with gcc-4.8.0 and graphite optimizations - /bin/sh .../work/texlive-20120701-source/texk/web2c/web2c/convert tangle syntax error: Last token = 44 (,), error buffer = `,', last id = `TANGLE' (not in symbol table). | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | eroen <erikdenstore+gbugs> |
Component: | Current packages | Assignee: | Gentoo Toolchain Maintainers <toolchain> |
Status: | RESOLVED WONTFIX | ||
Severity: | normal | CC: | martin, tex |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | build.log with gcc-4.8.0 |
Description
eroen
2013-04-10 05:08:44 UTC
Created attachment 345072 [details]
build.log with gcc-4.8.0
I have the same issue, and it is reproducable here, but only on amd64: On x86 there is no problem with gcc-4.8.0 (I have only gcc-4.8.0 installed, so I did not retry another gcc on amd64). I just realized that graphite (-graphite -floop-*) flags are enabled. Retried again without them, and it works: Obviously, "convert" miscompiled. So I guess that this bug can be closed as INVALID although perhaps gcc upstream might be interested to know about the "convert" miscompilation with graphite. As Martin said, this only occurs if graphite CFLAGS are enabled. In particular, enabling -fgraphite-identity or -floop-strip-mine along with -O2 causes build failure. Feel free to close as invalid/wontfix, although this could be seen as a regression in gcc-4.8.0 as compiling texlive-core with the same flags on gcc-4.7.2 works as expected. Just a heads up and since it is perhaps a bit simpler to reproduce: I had compiled vim-7.3.762 with gcc-4.8.0 and graphite, and after only a few tiny edits the whole edited file is complete rubbish afterwars. Without graphite, vim works as it should. So it seems graphite in gcc-4.8.0 is completely broken :( still broken gcc-4.8.1 app-text/texlive-core-2013-r1 gcc-4.9 is stable now, so throwing away older bugs we don't plan on doing backports for as this should be fixed w/4.9+. please re-open if it's still an issue with 4.9.3+ though. |