Bug#342126: gcc-4.0: gcc generates bad assembly code for simple code
Hi, Sorry by that, I have not noticed de '$'. It should be a '&'. Really, this is not a import bug. Thanks, Vagner. Falk Hueffner <[EMAIL PROTECTED]> escreveu: Vagner Pedrotti writes:> When I compile the following simple code, gcc fails with:> /tmp/ccySlj9q.s: Assembler messages:> /tmp/ccySlj9q.s:56: Error: missing or invalid immediate _expression_ `'> taken as 0> /tmp/ccySlj9q.s:56: Error: suffix or operands invalid for `call'This boils down to:void f() {$();}Apparently i386 doesn't like symbols starting with $. There shouldprobably be a better error message, but I wouldn't give it very highpriority... Or maybe there is some way to "escape" the symbol name?--
Falk
Yahoo! doce lar. Faça do Yahoo! sua homepage.
Bug#342245: gcc-3.4: boost 1.33.x FTBFS with "cannot handle R_PARISC_PCREL17F..."
Package: gcc-3.4 Version: 3.4.4-10 Severity: important hi, starting with version 3.4.4-10, gcc-3.4 makes boost 1.33.x FTBFS. /usr/bin/ld: bin/boost/libs/serialization/build/libboost_serialization.so/gcc/debug/shared-linkable-true/basic_iarchive.o(.gnu.linkonce.t._ZSt24__uninitialized_copy_auxIN9__gnu_cxx17__normal_iteratorIPN5boost7archive6detail19basic_iarchive_impl7aobjectESt6vectorIS6_SaIS6_SB_ET0_T_SD_SC_12__false_type+0xa0): cannot reach 0aae__ZSt10_ConstructIN5boost7archive6detail19basic_iarchive_impl7aobjectES4_EvPT_RKT0_+0, recompile with -ffunction-sections /usr/bin/ld: bin/boost/libs/serialization/build/libboost_serialization.so/gcc/debug/shared-linkable-true/basic_iarchive.o(.gnu.linkonce.t._ZSt24__uninitialized_copy_auxIN9__gnu_cxx17__normal_iteratorIPN5boost7archive6detail19basic_iarchive_impl7aobjectESt6vectorIS6_SaIS6_SB_ET0_T_SD_SC_12__false_type+0xa0): cannot handle R_PARISC_PCREL17F for void std::_Construct(boost::archive::detail::basic_iarchive_impl::aobject*, boost::archive::detail::basic_iarchive_impl::aobject const&) /usr/bin/ld: final link failed: Bad value collect2: ld returned 1 exit status the full log is available at http://buildd.debian.org/fetch.php?&pkg=boost&ver=1.33.0-5&arch=hppa&stamp=1132750731&file=log&as=raw. please let me know how to provide more details. unfortunately i'm currently not a toolchain expert. regards domenico -[ Domenico Andreoli, aka cavok --[ http://people.debian.org/~cavok/gpgkey.asc ---[ 3A0F 2F80 F79C 678A 8936 4FEE 0677 9033 A20E BC50 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#342267: gcc-4.0: boost 1.33.x FTBFS with "cannot handle R_PARISC_PCREL17F..."
Package: gcc-4.0 Version: n/a Severity: important hi, gcc-4.0 makes boost 1.33.x FTBFS on hppa. this bug is probably the same of #342245 for gcc-3.4, only that gcc-4.0 _never_ built 1.33.x on that architecture. /usr/bin/ld: bin/boost/libs/serialization/build/libboost_serialization.so/gcc/debug/shared-linkable-true/threading-multi/xml_oarchive.o(.gnu.linkonce.t._ZN5boost7archive6detail18interface_oarchiveINS0_12xml_oarchiveEElsIKNS0_12version_typeEEERS3_RT_[boost::archive::xml_oarchive& boost::archive::detail::interface_oarchive::operator<< (boost::archive::version_type const&)]+0x44): cannot reach 1f29__ZN5boost7archive18basic_xml_oarchiveINS0_12xml_oarchiveEE13save_overrideERKNS0_12version_typeEi+0, recompile with -ffunction-sections /usr/bin/ld: bin/boost/libs/serialization/build/libboost_serialization.so/gcc/debug/shared-linkable-true/threading-multi/xml_oarchive.o(.gnu.linkonce.t._ZN5boost7archive6detail18interface_oarchiveINS0_12xml_oarchiveEElsIKNS0_12version_typeEEERS3_RT_[boost::archive::xml_oarchive& boost::archive::detail::interface_oarchive::operator<< (boost::archive::version_type const&)]+0x44): cannot handle R_PARISC_PCREL17F for boost::archive::basic_xml_oarchive::save_override(boost::archive::version_type const&, int) /usr/bin/ld: final link failed: Bad value collect2: ld returned 1 exit status the full log is available at http://buildd.debian.org/fetch.php?&pkg=boost&ver=1.33.0-2&arch=hppa&stamp=1130099046&file=log&as=raw. i'm again available to delve further into this if only i get some hint of the direction to follow. anyway i'd be probably able to only extract more info, surely not to to fix the compiler itself. thanks domenico -[ Domenico Andreoli, aka cavok --[ http://people.debian.org/~cavok/gpgkey.asc ---[ 3A0F 2F80 F79C 678A 8936 4FEE 0677 9033 A20E BC50 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#342267: gcc-4.0: boost 1.33.x FTBFS with "cannot handle R_PARISC_PCREL17F..."
did you check the suggestion from the error message? please notice that the error message comes from the linker (binutils). Domenico Andreoli writes: > Package: gcc-4.0 > Version: n/a > Severity: important > > hi, > > gcc-4.0 makes boost 1.33.x FTBFS on hppa. this bug is probably the > same of #342245 for gcc-3.4, only that gcc-4.0 _never_ built 1.33.x on > that architecture. > > /usr/bin/ld: > bin/boost/libs/serialization/build/libboost_serialization.so/gcc/debug/shared-linkable-true/threading-multi/xml_oarchive.o(.gnu.linkonce.t._ZN5boost7archive6detail18interface_oarchiveINS0_12xml_oarchiveEElsIKNS0_12version_typeEEERS3_RT_[boost::archive::xml_oarchive& > > boost::archive::detail::interface_oarchive::operator<< > (boost::archive::version_type > const&)]+0x44): cannot reach > 1f29__ZN5boost7archive18basic_xml_oarchiveINS0_12xml_oarchiveEE13save_overrideERKNS0_12version_typeEi+0, > recompile with -ffunction-sections > /usr/bin/ld: > bin/boost/libs/serialization/build/libboost_serialization.so/gcc/debug/shared-linkable-true/threading-multi/xml_oarchive.o(.gnu.linkonce.t._ZN5boost7archive6detail18interface_oarchiveINS0_12xml_oarchiveEElsIKNS0_12version_typeEEERS3_RT_[boost::archive::xml_oarchive& > > boost::archive::detail::interface_oarchive::operator<< > (boost::archive::version_type > const&)]+0x44): cannot handle R_PARISC_PCREL17F for > boost::archive::basic_xml_oarchive::save_override(boost::archive::version_type > const&, int) > /usr/bin/ld: final link failed: Bad value > collect2: ld returned 1 exit status > > the full log is available at > http://buildd.debian.org/fetch.php?&pkg=boost&ver=1.33.0-2&arch=hppa&stamp=1130099046&file=log&as=raw. > > i'm again available to delve further into this if only i get some hint > of the direction to follow. anyway i'd be probably able to only extract > more info, surely not to to fix the compiler itself. > > thanks > domenico > > -[ Domenico Andreoli, aka cavok > --[ http://people.debian.org/~cavok/gpgkey.asc >---[ 3A0F 2F80 F79C 678A 8936 4FEE 0677 9033 A20E BC50 > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#342267: gcc-4.0: boost 1.33.x FTBFS with "cannot handle R_PARISC_PCREL17F..."
On Tue, Dec 06, 2005 at 05:41:14PM +0100, Matthias Klose wrote: > did you check the suggestion from the error message? please notice > that the error message comes from the linker (binutils). -ffunction-sections? yes, i did some time ago but nothing changed. i already submitted a bug report to binutils, #334497. i'd be happy to try with gcc 4.1, but i suppose it will not enter unstable before gcc 4.0 transition is finished. i'm now building boost 1.33.1 for experimental. then i will try to build it on paer.d.o, but i already know it is going to fail, recently i tried from upstream cvs. i will then try again with -ffunction-sections to be sure it really does not solve the problem. i also tried both gcc 3.4 and 4.0 with different levels of optimization, but again nothing changed. it looks like something deep in gcc vs. ld relationship. boost 1.32.0-6.1 built with binutils 2.16.1-2 and gcc 4.0.1-2. but boost 1.32.0+1.33.0-cvs20050727-1 cvs snapshot already broke with binutils 2.16.1-2 and gcc 4.0.1-3. it again built with binutils 2.16.1cvs20050902-1 and gcc 3.4.4-9 but suddenly broke again with gcc 3.4.4-10 and binutils 2.16.1cvs20050902-1 whatever bug/feature makes gcc fail the build, it entered in debian with gcc 4.0.1-3, gcc 3.4.4-10 or with some broken binutils. if i could install packages on paer.d.o, i surely would try different combinations of linker/compiler. cheers domenico -[ Domenico Andreoli, aka cavok --[ http://people.debian.org/~cavok/gpgkey.asc ---[ 3A0F 2F80 F79C 678A 8936 4FEE 0677 9033 A20E BC50 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
[Bug libstdc++/19664] libstdc++ headers should have pop/push of the visibility around the declarations
--- Comment #87 from pluto at agmk dot net 2005-12-06 17:05 --- current 4.1(+libstdc++ patch) works fine for PR21382 on amd64 and ppc. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19664 --- You are receiving this mail because: --- You are on the CC list for the bug, or are watching someone who is. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Results for 3.4.5 (Debian 3.4.5-1) testsuite on sparc-linux-gnu
LAST_UPDATED: Obtained from SVN: tags/gcc_3_4_5_release revision 107795 Native configuration is sparc-linux-gnu (sparky) === gpc tests === Running target any FAIL: fjf980a.pas FAIL: fjf980b.pas FAIL: fjf998r.pas === gpc Summary === # of tests4969 # of expected passes 4963 # of unexpected failures 3 # of unsupported tests3 /home/doko-local/gcc/3.4/gcc-3.4-3.4.5/build/gcc/xgpc version 20051116, based on gcc-3.4.5 (Debian 3.4.5-1) === acats tests === === acats Summary === # of expected passes1965 # of unexpected failures0 # of unsupported tests 357 === g++ tests === Running target unix WARNING: g++.dg/eh/simd-1.C compilation failed to produce executable WARNING: g++.dg/eh/simd-2.C compilation failed to produce executable XPASS: g++.dg/rtti/tinfo1.C scan-assembler _ZTIP9CTemplateIhE: XPASS: g++.dg/rtti/tinfo1.C scan-assembler-not .globl[ \\t]+_ZTIP9CTemplateIhE WARNING: g++.old-deja/g++.mike/p10769a.C compilation failed to produce executable WARNING: g++.old-deja/g++.other/enum5.C compilation failed to produce executable XPASS: g++.old-deja/g++.other/init5.C execution test WARNING: g++.old-deja/g++.pt/friend44.C compilation failed to produce executable === g++ Summary for unix === # of expected passes9878 # of unexpected successes 3 # of expected failures 70 # of unsupported tests 80 Running target unix/-m64 WARNING: g++.dg/eh/simd-1.C compilation failed to produce executable WARNING: g++.dg/eh/simd-2.C compilation failed to produce executable XPASS: g++.dg/rtti/tinfo1.C scan-assembler _ZTIP9CTemplateIhE: XPASS: g++.dg/rtti/tinfo1.C scan-assembler-not .globl[ \\t]+_ZTIP9CTemplateIhE WARNING: g++.old-deja/g++.mike/p10769a.C compilation failed to produce executable WARNING: g++.old-deja/g++.other/enum5.C compilation failed to produce executable XPASS: g++.old-deja/g++.other/init5.C execution test WARNING: g++.old-deja/g++.pt/friend44.C compilation failed to produce executable === g++ Summary for unix/-m64 === # of expected passes9878 # of unexpected successes 3 # of expected failures 70 # of unsupported tests 80 === g++ Summary === # of expected passes19756 # of unexpected successes 6 # of expected failures 140 # of unsupported tests 160 /home/doko-local/gcc/3.4/gcc-3.4-3.4.5/build/gcc/testsuite/../g++ version 3.4.5 (Debian 3.4.5-1) === g77 tests === Running target unix === g77 Summary for unix === # of expected passes1812 # of unsupported tests 6 Running target unix/-m64 === g77 Summary for unix/-m64 === # of expected passes1812 # of unsupported tests 6 === g77 Summary === # of expected passes3624 # of unsupported tests 12 /home/doko-local/gcc/3.4/gcc-3.4-3.4.5/build/gcc/testsuite/../g77 version 3.4.5 (Debian 3.4.5-1) === gcc tests === Running target unix WARNING: program timed out. FAIL: gcc.c-torture/compile/20001226-1.c -O2 (test for excess errors) WARNING: program timed out. FAIL: gcc.c-torture/compile/20001226-1.c -O3 -fomit-frame-pointer (test for excess errors) UNRESOLVED: gcc.c-torture/execute/simd-4.c execution, -O0 UNRESOLVED: gcc.dg/compat/vector-1 c_compat_x_tst.o-c_compat_y_tst.o link UNRESOLVED: gcc.dg/compat/vector-1 c_compat_x_tst.o-c_compat_y_tst.o execute UNRESOLVED: gcc.dg/compat/vector-2 c_compat_x_tst.o-c_compat_y_tst.o link UNRESOLVED: gcc.dg/compat/vector-2 c_compat_x_tst.o-c_compat_y_tst.o execute FAIL: gcc.dg/cleanup-8.c execution test FAIL: gcc.dg/cleanup-9.c execution test XPASS: gcc.dg/uninit-4.c uninitialized variable warning (test for bogus messages, line 26) === gcc Summary for unix === # of expected passes24964 # of unexpected failures4 # of unexpected successes 1 # of expected failures 79 # of unresolved testcases 5 # of untested testcases 7 # of unsupported tests 351 Running target unix/-m64 UNRESOLVED: gcc.c-torture/execute/simd-4.c execution, -O0 UNRESOLVED: gcc.c-torture/execute/va-arg-25.c execution, -O0 UNRESOLVED: gcc.c-torture/execute/va-arg-25.c execution, -O1 UNRESOLVED: gcc.c-torture/execute/va-arg-25.c execution, -O2 UNRESOLVED: gcc.c-torture/execute/va-arg-25.c execution, -O3 -fomit-frame-pointer UNRESOLVED: gcc.c-torture/execute/va-arg-25.c execution, -O3 -g UNRESOLVED: gcc.c-torture/execute/va-arg-25.c execution, -Os UNRESOLVED: gcc.dg/compat/vector-1 c_compat_x_tst.o-c_compat_y_tst.o link UNRESOLVED: gcc.dg/compat/vector-1 c_compat_x_tst.o-c_compat_y_tst.o execute UNRESOLVED: gcc.dg/compat/vector-2 c_compat_x_tst.o-c_compat_y_tst.o link UNRESOLVED: gcc.dg/compat/vector-2 c_compat_x_tst.o-c_compa
Results for 4.0.3 20051201 (prerelease) (Debian 4.0.2-5) testsuite on arm-unknown-linux-gnu
LAST_UPDATED: Thu Dec 1 18:58:03 UTC 2005 (revision 107827) Native configuration is arm-unknown-linux-gnu === libffi tests === Running target unix FAIL: libffi.call/closure_fn0.c (test for excess errors) WARNING: libffi.call/closure_fn0.c compilation failed to produce executable FAIL: libffi.call/closure_fn1.c (test for excess errors) WARNING: libffi.call/closure_fn1.c compilation failed to produce executable FAIL: libffi.call/closure_fn2.c (test for excess errors) WARNING: libffi.call/closure_fn2.c compilation failed to produce executable FAIL: libffi.call/closure_fn3.c (test for excess errors) WARNING: libffi.call/closure_fn3.c compilation failed to produce executable FAIL: libffi.call/closure_fn4.c (test for excess errors) WARNING: libffi.call/closure_fn4.c compilation failed to produce executable FAIL: libffi.call/closure_fn5.c (test for excess errors) WARNING: libffi.call/closure_fn5.c compilation failed to produce executable FAIL: libffi.call/cls_12byte.c (test for excess errors) WARNING: libffi.call/cls_12byte.c compilation failed to produce executable FAIL: libffi.call/cls_16byte.c (test for excess errors) WARNING: libffi.call/cls_16byte.c compilation failed to produce executable FAIL: libffi.call/cls_18byte.c (test for excess errors) WARNING: libffi.call/cls_18byte.c compilation failed to produce executable FAIL: libffi.call/cls_19byte.c (test for excess errors) WARNING: libffi.call/cls_19byte.c compilation failed to produce executable FAIL: libffi.call/cls_1_1byte.c (test for excess errors) WARNING: libffi.call/cls_1_1byte.c compilation failed to produce executable FAIL: libffi.call/cls_20byte.c (test for excess errors) WARNING: libffi.call/cls_20byte.c compilation failed to produce executable FAIL: libffi.call/cls_20byte1.c (test for excess errors) WARNING: libffi.call/cls_20byte1.c compilation failed to produce executable FAIL: libffi.call/cls_24byte.c (test for excess errors) WARNING: libffi.call/cls_24byte.c compilation failed to produce executable FAIL: libffi.call/cls_2byte.c (test for excess errors) WARNING: libffi.call/cls_2byte.c compilation failed to produce executable FAIL: libffi.call/cls_3_1byte.c (test for excess errors) WARNING: libffi.call/cls_3_1byte.c compilation failed to produce executable FAIL: libffi.call/cls_3byte1.c (test for excess errors) WARNING: libffi.call/cls_3byte1.c compilation failed to produce executable FAIL: libffi.call/cls_3byte2.c (test for excess errors) WARNING: libffi.call/cls_3byte2.c compilation failed to produce executable FAIL: libffi.call/cls_4_1byte.c (test for excess errors) WARNING: libffi.call/cls_4_1byte.c compilation failed to produce executable FAIL: libffi.call/cls_4byte.c (test for excess errors) WARNING: libffi.call/cls_4byte.c compilation failed to produce executable FAIL: libffi.call/cls_5byte.c (test for excess errors) WARNING: libffi.call/cls_5byte.c compilation failed to produce executable FAIL: libffi.call/cls_64byte.c (test for excess errors) WARNING: libffi.call/cls_64byte.c compilation failed to produce executable FAIL: libffi.call/cls_6byte.c (test for excess errors) WARNING: libffi.call/cls_6byte.c compilation failed to produce executable FAIL: libffi.call/cls_7byte.c (test for excess errors) WARNING: libffi.call/cls_7byte.c compilation failed to produce executable FAIL: libffi.call/cls_8byte.c (test for excess errors) WARNING: libffi.call/cls_8byte.c compilation failed to produce executable FAIL: libffi.call/cls_9byte1.c (test for excess errors) WARNING: libffi.call/cls_9byte1.c compilation failed to produce executable FAIL: libffi.call/cls_9byte2.c (test for excess errors) WARNING: libffi.call/cls_9byte2.c compilation failed to produce executable FAIL: libffi.call/cls_align_double.c (test for excess errors) WARNING: libffi.call/cls_align_double.c compilation failed to produce executable FAIL: libffi.call/cls_align_float.c (test for excess errors) WARNING: libffi.call/cls_align_float.c compilation failed to produce executable FAIL: libffi.call/cls_align_longdouble.c (test for excess errors) WARNING: libffi.call/cls_align_longdouble.c compilation failed to produce executable FAIL: libffi.call/cls_align_pointer.c (test for excess errors) WARNING: libffi.call/cls_align_pointer.c compilation failed to produce executable FAIL: libffi.call/cls_align_sint16.c (test for excess errors) WARNING: libffi.call/cls_align_sint16.c compilation failed to produce executable FAIL: libffi.call/cls_align_sint32.c (test for excess errors) WARNING: libffi.call/cls_align_sint32.c compilation failed to produce executable FAIL: libffi.call/cls_align_sint64.c (test for excess errors) WARNING: libffi.call/cls_align_sint64.c compilation failed to produce executable FAIL: libffi.call/cls_align_uint16.c (test for excess errors) WARNING: libffi.call/cls_align_uint16.c compilation failed to produce executable FAIL: libffi.call/cls_align_uint32.c (test for excess errors) WARNING: libffi.call/cls_align_uint32.c compilation failed to produce
Bug#173513: [Bug tree-optimization/9079] [tree-ssa] Inline constant function pointers
-- pinskia at gcc dot gnu dot org changed: What|Removed |Added Last reconfirmed|2005-09-07 17:38:57 |2005-12-07 03:05:19 date|| http://gcc.gnu.org/bugzilla/show_bug.cgi?id=9079 --- You are receiving this mail because: --- You reported the bug, or are watching the reporter. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#181096: [Bug tree-optimization/9814] gcc fails to optimise if (l&2) l|=2 away
--- Comment #7 from pinskia at gcc dot gnu dot org 2005-12-07 03:12 --- Once fold does (a&b)!=0?a|b:a to a and PR 25290 is fixed then this will be caught at the tree level. There are most likely others like this too. -- pinskia at gcc dot gnu dot org changed: What|Removed |Added BugsThisDependsOn||25290 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=9814 --- You are receiving this mail because: --- You reported the bug, or are watching the reporter. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
[Bug c++/6634] wrong parsing of "long long double"
-- pinskia at gcc dot gnu dot org changed: What|Removed |Added Last reconfirmed|2005-09-04 18:20:30 |2005-12-07 04:47:52 date|| http://gcc.gnu.org/bugzilla/show_bug.cgi?id=6634 --- You are receiving this mail because: --- You are on the CC list for the bug, or are watching someone who is. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
