Bug#347508: libstdc++6-4.0-dev: 4.0.3/libstdc++.a BFD: sh_link in section XXX is incorrect
unable to reproduce on ia64 with 3.4.6-1, 4.0.3, 4.1.0. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
gcj-4.1 4.1.0-1 MIGRATED to testing
FYI: The status of the gcj-4.1 source package in Debian's testing distribution has changed. Previous version: (not in testing) Current version: 4.1.0-1 -- This email is automatically generated; [EMAIL PROTECTED] is responsible. See http://people.debian.org/~henning/trille/ for more information. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#361942: more information
The property can be controlled, so I supopose the question becomes, what should be the default value? Sorry I dont know enough, is this a bug or not? [EMAIL PROTECTED]:~$ gij-4.1 -Djava.home=/usr GetJVMInfo java.version= 1.4.2 java.vendor= Free Software Foundation, Inc. java.home=/usr [EMAIL PROTECTED]:~$ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
[Bug middle-end/26557] [4.0 Regression] ICE in simplify_subreg
--- Comment #9 from kazu at gcc dot gnu dot org 2006-04-11 23:47 --- Subject: Bug 26557 Author: kazu Date: Tue Apr 11 23:47:35 2006 New Revision: 112870 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=112870 Log: Backport from mainline. 2006-03-13 Roger Sayle <[EMAIL PROTECTED]> PR middle-end/26557 * gcc/stmt.c (emit_case_nodes): Handle the case where the index is a CONST_INT, where the comparison mode is specified by the index type. 2006-03-13 Roger Sayle <[EMAIL PROTECTED]> PR middle-end/26557 * gcc/gcc.c-torture/compile/switch-1.c: New test case. Added: branches/csl/sourcerygxx-4_1/gcc/testsuite/gcc.c-torture/compile/switch-1.c Modified: branches/csl/sourcerygxx-4_1/ChangeLog.csl branches/csl/sourcerygxx-4_1/gcc/stmt.c -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26557 --- 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#361024: 361024: and lack of feedback
On Tue, Apr 11, 2006 at 07:21:49PM -0700, Gordon Haverland wrote: > Occasionally I get an email from someone who is reporting back to > many people, but in general I have gotten NO FEEDBACK on this bug > report! It apparently wasn't reproducible to the person fielding > the bug report, but it is reproducible here. I asked, what can I > do to send you info to fix this? I get NOTHING! Someone else > reports on setting LD_DEBUG=all and running things I try this, > and get a HUGE output file. So, I send in a minimal report on > this, and hear NOTHING! A series of patched debs at > http://people.debian.org/~doko/tmp/ is suggested. I download and > install those. I get an error about cpp dependence, which I > report. No comment on this cpp dependence! And, if nothing > else, my system is even less usable than before. Apt-proxy won't > run (TLS errors), and so I try to bring things back to only using > apt to get the various packages files and compare things. I > still get tons of errors. > > AND STILL THERE IS NO RESPONSE TO ANYTHING I'VE SENT IN! Are you > looking for me to give up on Debian? Can't I get some feedback > as to what is happening? I am not expecting miracles. I would > like to help, if I can. But it is just some bloody black hole > that I report to! > > Is the only option to upgrade to a 2.6 kernel? Looking at the bug report it looks like there is lots of activity. Hardly what I would call no response to anything. Certainly TLS requires a 2.6 kernel. If libstdc++6 requires TLS for some reason, then it requries a 2.6 kernel. That is probably a bug if that is the case. Len Sorensen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#361445: Log for failed build of kdepim_4:3.5.2-1
PIC: > Automatic build of kdepim_4:3.5.2-1 on em64t by sbuild/amd64 1.112 ... > g++ -shared -nostdlib /usr/lib/../lib64/crti.o > /usr/lib/gcc-snapshot/lib/gcc/x86_64-linux-gnu/4.2.0/crtbeginS.o > .libs/libkleopatra_la.all_cpp.o -Wl,--whole-archive > kleo/.libs/libkleopatra_core.a > backends/qgpgme/.libs/libkleopatra_backend_qgpgme.a > backends/chiasmus/.libs/libkleopatra_backend_chiasmus.a > ui/.libs/libkleopatra_ui.a -Wl,--no-whole-archive -Wl,--rpath > -Wl,/build/tbm/kdepim-3.5.2/build-tree/obj-x86_64-linux-gnu/libkdenetwork/qgpgme/.libs > -Wl,--rpath -Wl,/usr/lib/gcc-snapshot/lib64 -Wl,--rpath > -Wl,/usr/lib/gcc-snapshot/lib64 -L/usr/lib -L/usr/share/qt3/lib > -L/usr/X11R6/lib -L/lib ../../libkdenetwork/qgpgme/.libs/libqgpgme.so > /usr/lib/libkio.so /usr/lib/libkdeui.so > -L/usr/lib/gcc-snapshot/lib/gcc/x86_64-linux-gnu/4.2.0 > -L/usr/lib/gcc-snapshot/lib/gcc/x86_64-linux-gnu/4.2.0/../../../../lib64 > -L/lib/../lib64 -L/usr/lib/../lib64 > -L/usr/lib/gcc-snapshot/lib/gcc/x86_64-linux-gnu/4.2.0/../../.. > /usr/lib/gcc-snapshot/lib64/libstdc++.so -lm -lc -lgcc_s > /usr/lib/gcc-snapshot/lib/gcc/x86_64-linux-gnu/4.2.0/crtendS.o > /usr/lib/../lib64/crtn.o -Wl,-soname -Wl,libkleopatra.so.1 -o > .libs/libkleopatra.so.1.0.0 > /usr/bin/ld: > backends/chiasmus/.libs/libkleopatra_backend_chiasmus.a(libkleopatra_backend_chiasmus_la.all_cpp.o): > relocation R_X86_64_PC32 against `QValueListPrivate int>::QValueListPrivate()' can not be used when making a shared object; > recompile with -fPIC > /usr/bin/ld: final link failed: Bad value > collect2: ld returned 1 exit status > make[5]: *** [libkleopatra.la] Error 1 -- Martin Michlmayr http://www.cyrius.com/
Bug#361445: Log for failed build of moc_2.4.0-1
More PIC: > Automatic build of moc_2.4.0-1 on em64t by sbuild/amd64 1.112 ... > /bin/sh ../../libtool --tag=CC --mode=link x86_64-linux-gnu-gcc -g -Wall -O2 > -export-dynamic -o libffmpeg_decoder.la -rpath /usr/lib/moc/decoder_plugins > -module -avoid-version libffmpeg_decoder_la-ffmpeg.lo -lavformat -lavcodec > -lavutil -lvorbis -lvorbisenc -ltheora -logg -ldts -la52 -lraw1394 > -ldc1394_control -lgsm -lz -lm -lm > x86_64-linux-gnu-gcc -shared .libs/libffmpeg_decoder_la-ffmpeg.o -lavformat > -lavcodec -lavutil /usr/lib/libvorbis.so /usr/lib/libvorbisenc.so > /usr/lib/libtheora.so /usr/lib/libogg.so -ldts /usr/lib/liba52.so > /usr/lib/libraw1394.so -ldc1394_control -lgsm -lz -lm -Wl,-soname > -Wl,libffmpeg_decoder.so -o .libs/libffmpeg_decoder.so > /usr/bin/ld: /usr/lib/../lib64/libavformat.a(utils.o): relocation R_X86_64_32 > against `first_iformat' can not be used when making a shared object; > recompile with -fPIC > /usr/lib/../lib64/libavformat.a: could not read symbols: Bad value > collect2: ld returned 1 exit status > make[4]: *** [libffmpeg_decoder.la] Error 1 -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#361441: Log for failed build of openexr_1.2.2-4.2
and here: > Automatic build of openexr_1.2.2-4.2 on em64t by sbuild/amd64 1.112 ... > g++ -DPACKAGE_NAME=\"\" -DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\" > -DPACKAGE_STRING=\"\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE=\"OpenEXR\" > -DVERSION=\"1.2.2\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 > -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 > -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 > -DSTDC_HEADERS=1 -DHAVE_LIMITS_H=1 -DHAVE_UNISTD_H=1 -DHAVE_STRERROR=1 > -DHAVE_IOS_BASE=1 -DHAVE_COMPLETE_IOMANIP=1 -DHAVE_STL_LIMITS=1 -I. -I. -pipe > -g -Wall -O2 -c IexBaseExc.cpp -fPIC -DPIC -o .libs/IexBaseExc.o > IexBaseExc.cpp: In constructor 'Iex::BaseExc::BaseExc(const char*)': > IexBaseExc.cpp:69: internal compiler error: in add_virtual_operand, at > tree-ssa-operands.c:1354 > Please submit a full bug report, > with preprocessed source if appropriate. > See http://gcc.gnu.org/bugs.html> for instructions. > make[2]: *** [IexBaseExc.lo] Error 1 -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#361441: Log for failed build of kdelibs_4:3.5.2-2
and here: > Automatic build of kdelibs_4:3.5.2-2 on em64t by sbuild/amd64 1.112 ... > g++ -DHAVE_CONFIG_H -I. -I/build/tbm/kdelibs-3.5.2/./kjs -I.. -I../dcop > -I../kdecore -I../kio/kssl -I. -I/build/tbm/kdelibs-3.5.2/./dcop > -I/build/tbm/kdelibs-3.5.2/./libltdl -I/build/tbm/kdelibs-3.5.2/./kdefx > -I../kdecore -I/build/tbm/kdelibs-3.5.2/./kdecore > -I/build/tbm/kdelibs-3.5.2/./kdeui -I/build/tbm/kdelibs-3.5.2/./kio > -I/build/tbm/kdelibs-3.5.2/./kio/kio -I/build/tbm/kdelibs-3.5.2/./kio/kfile > -I/build/tbm/kdelibs-3.5.2/. -I/usr/share/qt3/include -I. -I/usr/include/kde > -DQT_THREAD_SUPPORT -D_REENTRANT -Wno-long-long -Wundef -ansi > -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -Wcast-align -Wconversion -Wchar-subscripts > -Wall -W -Wpointer-arith -DNDEBUG -DNO_DEBUG -O2 -g -Wall -O2 > -DDEBIAN_VERSION=4:3.5.2-2 -Wformat-security -Wmissing-format-attribute > -Wno-non-virtual-dtor -fno-exceptions -fno-check-new -fno-common > -DQT_CLEAN_NAMESPACE -DQT_NO_ASCII_CAST -DQT_NO_STL -DQT_NO_COMPAT > -DQT_NO_TRANSLATION -c libkjs_la.all_cpp.cpp -fPIC -DPIC -o > .libs/libkjs_la.all_cpp.o > In file included from libkjs_la.all_cpp.cpp:6: > grammar.tab.c:335:6: warning: "YYENABLE_NLS" is not defined > /build/tbm/kdelibs-3.5.2/./kjs/dtoa.cpp: In function 'Bigint* Balloc(int)': > /build/tbm/kdelibs-3.5.2/./kjs/dtoa.cpp:528: warning: comparison between > signed and unsigned integer expressions > /build/tbm/kdelibs-3.5.2/./kjs/dtoa.cpp: In function 'char* kjs_dtoa(double, > int, int, int*, int*, char**)': > /build/tbm/kdelibs-3.5.2/./kjs/dtoa.cpp:2643: internal compiler error: in > add_virtual_operand, at tree-ssa-operands.c:1354 > Please submit a full bug report, > with preprocessed source if appropriate. > See http://gcc.gnu.org/bugs.html> for instructions. > make[4]: *** [libkjs_la.all_cpp.lo] Error 1 > make[4]: Leaving directory `/build/tbm/kdelibs-3.5.2/obj-x86_64-linux-gnu/kjs' -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#361602: Log for failed build of octave2.9_2.9.4-13
and here: > Automatic build of octave2.9_2.9.4-13 on em64t by sbuild/amd64 1.112 ... > /usr/bin/g++ -c -fPIC -I. -I.. -I../liboctave -I../src -I../libcruft/misc > -DHAVE_CONFIG_H -Wall -W -Wshadow -O2 load-save.cc -o pic/load-save.o > ls-hdf5.h:70: warning: unused parameter 'prot' > load-save.cc: In function 'octave_value_list Fsave(const octave_value_list&, > int)': > load-save.cc:1689: error: ambiguous overload for 'operator==' in 'file. > gzofstream::rdbuf()->gzfilebuf::.std::basic_streambuf<_CharT, > _Traits>::pubseekoff [with _CharT = char, _Traits = > std::char_traits](0l, _S_cur, std::operator|(_S_in, _S_out)) == > std::fpos<__mbstate_t>(0l)' > load-save.cc:1689: note: candidates are: operator==(std::streamoff, > std::streamoff) > ../liboctave/oct-inttypes.h:585: note: bool operator==(const > octave_int&, const octave_int&) > ../liboctave/oct-inttypes.h:585: note: bool operator==(const > octave_int&, const octave_int&) > ../liboctave/oct-inttypes.h:586: note: bool operator==(const > octave_int&, const octave_int&) > ../liboctave/oct-inttypes.h:586: note: bool operator==(const > octave_int&, const octave_int&) > ../liboctave/oct-inttypes.h:587: note: bool operator==(const > octave_int&, const octave_int&) > ../liboctave/oct-inttypes.h:587: note: bool operator==(const > octave_int&, const octave_int&) > ../liboctave/oct-inttypes.h:589: note: bool operator==(const > octave_int&, const octave_int&) > ../liboctave/oct-inttypes.h:589: note: bool operator==(const > octave_int&, const octave_int&) > ../liboctave/oct-inttypes.h:590: note: bool operator==(const > octave_int&, const octave_int&) > ../liboctave/oct-inttypes.h:590: note: bool operator==(const > octave_int&, const octave_int&) > ../liboctave/oct-inttypes.h:591: note: bool operator==(const > octave_int&, const octave_int&) > ../liboctave/oct-inttypes.h:591: note: bool operator==(const > octave_int&, const octave_int&) > ../liboctave/oct-inttypes.h:592: note: bool operator==(const > octave_int&, const octave_int&) > ../liboctave/oct-inttypes.h:592: note: bool operator==(const > octave_int&, const octave_int&) > ../liboctave/oct-inttypes.h:624: note: bool operator==(const > octave_int&, const octave_int&) > ../liboctave/oct-inttypes.h:624: note: bool operator==(const > octave_int&, const octave_int&) > load-save.cc:1711: error: ambiguous overload for 'operator==' in 'file. > std::basic_ofstream<_CharT, _Traits>::rdbuf [with _CharT = char, _Traits = > std::char_traits]()->std::basic_filebuf > >::.std::basic_streambuf<_CharT, _Traits>::pubseekoff [with _CharT > = char, _Traits = std::char_traits](0l, _S_cur, std::operator|(_S_in, > _S_out)) == std::fpos<__mbstate_t>(0l)' > load-save.cc:1711: note: candidates are: operator==(std::streamoff, > std::streamoff) > ../liboctave/oct-inttypes.h:585: note: bool operator==(const > octave_int&, const octave_int&) > ../liboctave/oct-inttypes.h:585: note: bool operator==(const > octave_int&, const octave_int&) > ../liboctave/oct-inttypes.h:586: note: bool operator==(const > octave_int&, const octave_int&) > ../liboctave/oct-inttypes.h:586: note: bool operator==(const > octave_int&, const octave_int&) > ../liboctave/oct-inttypes.h:587: note: bool operator==(const > octave_int&, const octave_int&) > ../liboctave/oct-inttypes.h:587: note: bool operator==(const > octave_int&, const octave_int&) > ../liboctave/oct-inttypes.h:589: note: bool operator==(const > octave_int&, const octave_int&) > ../liboctave/oct-inttypes.h:589: note: bool operator==(const > octave_int&, const octave_int&) > ../liboctave/oct-inttypes.h:590: note: bool operator==(const > octave_int&, const octave_int&) > ../liboctave/oct-inttypes.h:590: note: bool operator==(const > octave_int&, const octave_int&) > ../liboctave/oct-inttypes.h:591: note: bool operator==(const > octave_int&, const octave_int&) > ../liboctave/oct-inttypes.h:591: note: bool operator==(const > octave_int&, const octave_int&) > ../liboctave/oct-inttypes.h:592: note: bool operator==(const > octave_int&, const octave_int&) > ../liboctave/oct-inttypes.h:592: note: bool operator==(const > octave_int&, const octave_int&) > ../liboctave/oct-inttypes.h:624: note: bool operator==(const > octave_int&, const octave_int&) > ../liboctave/oct-inttypes.h:624: note: bool operator==(const > octave_int&, const octave_int&) > load-save.cc: At global scope: > load-save.cc:1910: error: inlined_to pointer is set but no predecesors found > virtual
Processed: fixed upstream
Processing commands for [EMAIL PROTECTED]: > tags 361715 + fixed-upstream Bug#361715: segfaults compiling pari_2.1.7-2 There were no tags set. Tags added: fixed-upstream > -- Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#361715: fixed indeed
Falk, I can confirm that these segfaults are fixed. I just tried with 20060408 and they're gone. -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#361024: 361024: and lack of feedback
On Wednesday 12 April 2006 12:37, Some have written: > There seems to be tons of feedback with that bug report. [ Or similar. ] I must get better at phrasing things then. There is a lot of feedback in the bug report. However, within the bug report there are still many questions which are never answered or commented upon. As far as feedback goes, a couple of people responding to issues in the bug report, did cc me a copy of the email they submitted. Most people responding to issues in the bug report, did not cc me anything. So, I might recieve an email which seemed to be related to what I had asked, didn't answer my questions. Thinking that my part of the questions had been solved and this being something more involved, I would look at the bug report to find that usually no, what I had asked still hadn't been answered, but someone elses related problem with this same bug had been answered or commented upon. For instance, someone had suggested running whatever troublesome program with LD_DEBUG=all in the environment. Fine, I did that with an apt-get upgrade. This produced a 36 MB file. I mentioned how big the file was, and where the error message was in that file. Nobody said anything about this file after that. I still have this file. I gather it is of no use, and that I can delete it. I am not necessarily in a hurry to upgrade to a 2.6 kernel. If there are things I can do here, to help get rid of this bug, I am probably willing to try. No, I have no experience at debugging things like libc. I do have more than 25 years experience at programming, mostly number crunching. But unless someone suggests an action plan, I am not going to try and find/solve this thing on my own. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Results for 3.4.6 (Debian 3.4.6-1) testsuite on hppa-linux-gnu
LAST_UPDATED: Obtained from SVN: tags/gcc_3_4_6_release revision 111785 Native configuration is hppa-linux-gnu (sarti) === gpc tests === Running target any FAIL: avo2a.pas FAIL: avo2b.pas === gpc Summary === # of tests438 # of expected passes 434 # of unexpected failures 2 # of unsupported tests2 /build/buildd/gcc-3.4-3.4.6/build/gcc/xgpc version 20060215, based on gcc-3.4.6 (Debian 3.4.6-1) === g++ tests === Running target unix XPASS: g++.old-deja/g++.other/init5.C execution test === g++ Summary === # of expected passes9923 # of unexpected successes 1 # of expected failures 67 # of unsupported tests 83 /build/buildd/gcc-3.4-3.4.6/build/gcc/testsuite/../g++ version 3.4.6 (Debian 3.4.6-1) === g77 tests === Running target unix === g77 Summary === # of expected passes1812 # of unsupported tests 6 /build/buildd/gcc-3.4-3.4.6/build/gcc/testsuite/../g77 version 3.4.6 (Debian 3.4.6-1) === gcc tests === Running target unix === gcc Summary === # of expected passes23368 # of expected failures 69 # of unsupported tests 302 /build/buildd/gcc-3.4-3.4.6/build/gcc/xgcc version 3.4.6 (Debian 3.4.6-1) === libstdc++ tests === Running target unix XPASS: 22_locale/locale/cons/12658_thread.cc execution test XPASS: 26_numerics/c99_classification_macros_c.cc (test for excess errors) === libstdc++ Summary === # of expected passes2737 # of unexpected successes 2 # of expected failures 5 Compiler version: 3.4.6 (Debian 3.4.6-1) Platform: hppa-linux-gnu configure flags: -v --enable-languages=c,c++,f77,pascal --prefix=/usr --libexecdir=/usr/lib --with-gxx-include-dir=/usr/include/c++/3.4 --enable-shared --with-system-zlib --enable-nls --without-included-gettext --program-suffix=-3.4 --enable-__cxa_atexit --enable-clocale=gnu --enable-libstdcxx-debug hppa-linux-gnu BOOT_CFLAGS=-O2 Build Dependencies: Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed |/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad) ||/ Name Version Description +++-==-===-== ii binutils 2.16.1cvs20060117-1 The GNU assembler, linker and binary utilities Patches that Debian applied in this version: gcc-textdomain: Set gettext's domain and textdomain to the versioned package name. rename-info-files: Allow transformations on info file names. Reference the transformed info file names in the texinfo files. libstdc++-pic: Build and install libstdc++_pic.a library. libstdc++-doclink: adjust hrefs to point to the local documentation libstdc++-doxygen-syntax: fix doxygen syntax error in header that causes segfaults with some versions amd64-specs: On x86-64 use 64bits mode assembly except with -m32. gccbug: Use sensible-editor instead of vi as fallback editor gccbug-posix: Make gccbug POSIX compliant (patch by David Weinehall) http://www.opengroup.org/onlinepubs/009695399/utilities/test.html hppa-toplevel: For hppa-linux enable libgcj and dependent libs in the toplevel directory hppa-libffi: libffi support for hppa hppa-libjava: Enable libjava support for hppa hppa-libjava-update: MD_FALLBACK_FRAME_STATE_FOR definition for pa32-linux fastjar-update: Implement fastjar -u (PR 7854). fastjar-version: Append GCC version to the fastjar version string. boehm-gc-nocheck: Disable the boehm-gc testsuite. Hangs forever on this architecture libltdl: * libltdl.dpatch: Search the versioned extension, when loading a shared library (i.e. gij looks for .so.5 for loading additional libraries like the GTK based AWT peers. m68k-update: Add two m68k specfic patches backported from 4.0 concerning wrong code generation (Richard Zidlicky). libf2c-mxunit: libf2c/libI77/fio.c: Set MXUNIT to 1000. arm-bigendian: cpu-default-i486: set default 32bit ix86 architecture to i486 libffi-soversion: Install libffi with soversion 3. gpc-3.x: The gpc patch from the gpc tarball. gpc-doc: gpc documentation: Fix hyperlinks to the example files. gpc-updates: gpc-names: versioned gpc names libffi-mips: libffi mips update libjava-mips: libjava-mips patch from Thiemo Seufer <[EMAIL PROTECTED]> libstdc++-mips-atomic: Fix libstdc++ atomic ops for mips/mipsel link-libs: reporting: Add Debian URL for bug reporting isntructions. gcc-version: Add package identification to the gcc version string configure-deplibs_check_method: In all configure scripts for libraries, generated with autoconf2.13, use deplibs_check_method=pass_all unconditionally for all linux architectures. Counting all warnings, th
[Bug c++/27094] [4.0/4.1/4.2 Regression] tree check: expected tree_list, have omp_return in build_call
--- Comment #6 from jakub at gcc dot gnu dot org 2006-04-12 11:46 ---
It is a GC problem, when build_over_call calls mark_used, it certainly doesn't
expect mark_used to do a gcc_collect underneath it, as it has several tree
pointers stored in local variables. I guess build_over_call isn't the only
place that trusts mark_used doesn't do that, e.g. build_call,
build_op_delete_call, finish_eh_spec_block etc. likely suffer from the same
problem.
The call chain that leads to ggc_collect is mark_used ->
{synthetize_method,instantiate_decl} -> expand_or_defer_fn ->
cgraph_finalize_function -> ggc_collect.
So, either we change mark_used to never trigger GC from underneath us
(e.g. by function_depth++; synthetise_method (...); function_depth--; and
probably similarly for instantiate_decl), or we add an argument to mark_used
if it is ok to ggc_collect (similarly to cgraph_finalize_function's NESTED
argument), or we change all mark_used callers that might suffer from this
(either by adding function_depth++/function_depth-- around the call, or by
registering its temporaries with GC before calling mark_used).
--
jakub at gcc dot gnu dot org changed:
What|Removed |Added
CC||jason at redhat dot com,
||mark at codesourcery dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27094
--- 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]
