Re: libstdc++, -m64 and can't find atom for N_GSYM stabs
Eric Christopher <[EMAIL PROTECTED]> writes: >> Once the noise from those linker warnings is removed from the libstdc++-v3 >> testsuite >> results at -m64 on Darwin PPC, we find that the failures drop from 54 to >> just 6. So >> we actually only have four additional libstdc++-v3 testsuite failures at -m64 >> compared to -m32. These are... >> >> FAIL: 21_strings/basic_string/cons/char/1.cc execution test >> FAIL: 21_strings/basic_string/cons/wchar_t/1.cc execution test >> FAIL: 21_strings/basic_string/insert/char/1.cc execution test >> FAIL: 21_strings/basic_string/insert/wchar_t/1.cc execution test >> >> which certainly would appear as if they are all related bugs. Can you try >> the above check on x86_64 and see how many regressions you have when the >> linker warnings suppressed? > > For i386 vs x86_64 I'm getting a different set of pass/fail between > the two. I do, however, have those 4 failures on x86_64 and not on > i386. Those come AFAIR from a wrong locale path. I'm not sure whether a bug is filed for this or whether it was only discussed at some mailing list, Andreas -- Andreas Jaeger, [EMAIL PROTECTED], http://www.suse.de/~aj/ SUSE Linux Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126 pgpI0xO3mlyBq.pgp Description: PGP signature
Re: http://gcc.gnu.org/install/configure.html
On Sun, 27 Aug 2006, Richard Guenther wrote: > The problem is that installation instructions (and internals manuals) > are only available for trunk, not for released versions. These aren't online, but are part of the release tarballs. We could add generation of the installation documentation to the magic in maintainer-scripts/update_web_docs_svn, but I'm not sufficiently familiar with that script to do so without undue risk. I had a look, but I'm not really too familiar with this script. Something like the patch below might come close (it just omits the postprocessing of these version specific web pages of the installation docs). Joseph, what do you think? Gerald Index: update_web_docs_svn === --- update_web_docs_svn (revision 116641) +++ update_web_docs_svn (working copy) @@ -157,7 +157,7 @@ done fi -# And copy the resulting files to the web server +# Copy the resulting files to the web server. for file in */*.html *.ps *.pdf *.tar; do if [ -f $DOCSDIR/$file ]; then cat $DOCSDIR/$file | @@ -177,19 +177,26 @@ cd $DOCSDIR -# Finally, generate the installation documentation +# And generate version-specific installation documentation. +SOURCEDIR=$WORKDIR/gcc/gcc/doc +DESTDIR=$DOCSDOR/install +export SOURCEDIR +export DESTDIR +$WORKDIR/gcc/gcc/doc/install.texi2html + +# Finally, generate the primary installation documentation. if [ "$RELEASE" = "trunk" ]; then SOURCEDIR=$WORKDIR/gcc/gcc/doc DESTDIR=$WWWBASE_PREFORMATTED/install export SOURCEDIR export DESTDIR $WORKDIR/gcc/gcc/doc/install.texi2html - - # Preprocess the entire web site, not just the install docs! - echo "Invoking $WWWPREPROCESS" - $WWWPREPROCESS |grep -v '^ Warning: Keeping' fi +# Preprocess the entire web site, not just the install docs! +echo "Invoking $WWWPREPROCESS" +$WWWPREPROCESS | grep -v '^ Warning: Keeping' + # Clean up behind us. rm -rf $WORKDIR
Re: http://gcc.gnu.org/install/configure.html
On Sat, 2 Sep 2006, Gerald Pfeifer wrote: > On Sun, 27 Aug 2006, Richard Guenther wrote: > > The problem is that installation instructions (and internals manuals) > > are only available for trunk, not for released versions. > > These aren't online, but are part of the release tarballs. > > We could add generation of the installation documentation to the magic in > maintainer-scripts/update_web_docs_svn, but I'm not sufficiently familiar > with that script to do so without undue risk. > > I had a look, but I'm not really too familiar with this script. Something > like the patch below might come close (it just omits the postprocessing of > these version specific web pages of the installation docs). > > Joseph, what do you think? The traditional approach was to include statements about different versions in the trunk install manual where appropriate, and where that didn't suffice to refer to the documentation included in the release tarballs. (Not an objection.) > +DESTDIR=$DOCSDOR/install ^ typo -- Joseph S. Myers [EMAIL PROTECTED]
Meaning of (set (reg:CC condition_codes_reg) (ge (op0) (op1)))
What does this instruction mean? (set (reg:CC 13 cc) (ge (mem/c/i:HI (plus:HI (reg/f:HI 15 argp) (const_int 2 [0x2])) [2 x+0 S2 A16]) (const_int 0 [0x0]))) It is one of combine's creations. The manual defines the meaning of GE this way: (gt:m x y) STORE_FLAG_VALUE if the x is greater than y. If they are fixed-point, the comparison is done in a signed sense. (gtu:m x y) Like gt but does unsigned comparison, on fixed-point numbers only. (ge:m x y) (geu:m x y) Like gt and gtu but test for "greater than or equal". The (reg:CC 13 cc) part is the condition code register. But I have no idea what it means to set that register to a constant (such as STORE_FLAG_VALUE). -- Rask Ingemann Lambertsen
Copyright assignment form
Please send me the copyright assignment form I need to contribute to GCC. -- Rask Ingemann Lambertsen
gcc-4.2-20060902 is now available
Snapshot gcc-4.2-20060902 is now available on ftp://gcc.gnu.org/pub/gcc/snapshots/4.2-20060902/ and on various mirrors, see http://gcc.gnu.org/mirrors.html for details. This snapshot has been generated from the GCC 4.2 SVN branch with the following options: svn://gcc.gnu.org/svn/gcc/trunk revision 116661 You'll find: gcc-4.2-20060902.tar.bz2 Complete GCC (includes all of below) gcc-core-4.2-20060902.tar.bz2 C front end and core compiler gcc-ada-4.2-20060902.tar.bz2 Ada front end and runtime gcc-fortran-4.2-20060902.tar.bz2 Fortran front end and runtime gcc-g++-4.2-20060902.tar.bz2 C++ front end and runtime gcc-java-4.2-20060902.tar.bz2 Java front end and runtime gcc-objc-4.2-20060902.tar.bz2 Objective-C front end and runtime gcc-testsuite-4.2-20060902.tar.bz2The GCC testsuite Diffs from 4.2-20060826 are available in the diffs/ subdirectory. When a particular snapshot is ready for public consumption the LATEST-4.2 link is updated and a message is sent to the gcc list. Please do not use a snapshot before it has been announced that way.
RE: call dsymutil on darwin when compiling and linking in single step
Geoff, Does the patch you propose in... http://gcc.gnu.org/ml/gcc-patches/2006-09/msg00057.html eliminate the "can't find atom for N_GSYM stabs" warnings in ld64? I ask because you that... This is necessary since otherwise the debugger expects to find the DWARF information in the .o file, but the compiler will have deleted it. ...which makes me wonder if this could be the case. Jack
Successful GCC 4.1.1 i686-pc-mingw32 build+install
$ config.guess i686-pc-mingw32 F:\Compilers\MinGW\bin>gcc -v Using built-in specs. Target: i686-pc-mingw32 Configured with: ../gcc-4.1.1/configure --prefix=/mingw --disable-shared --enable-threads --enable-languages=c,c++ --disable-win32-registry --disable-nls Thread model: win32 gcc version 4.1.1 I built using this command line: make CFLAGS="-O2 -fomit-frame-pointer" CXXFLAGS="-mthreads -fno-omit-frame-pointer -O2" LDFLAGS=-s bootstrap I used MinGW32's GCC 3.4.5 distribution and mSYS 1.0, plus assorted tools. The build process encountered ONE fatal error: In /gcc/Makefile:1277, ORIGINAL_LD_FOR_TARGET was incorrectly set as "./f:/Compilers/MinGW/bin/ld.exe". The build was successful after I changed it to "/f/Compilers/MinGW/bin/ld", following the pattern of ORIGINAL_AS_FOR_TARGET which was correctly set. (MinGW is installed in /f/Compilers/MinGW for my system; others might see something like /c/MinGW or /mingw.)
Re: GCC 4.3 Projects Page
On 9/1/06, Mark Mitchell <[EMAIL PROTECTED]> wrote: Joe Buck wrote: > On Fri, Sep 01, 2006 at 03:56:30PM -0700, Mark Mitchell wrote: >> Please add your project page to the bottom of: >> >> http://gcc.gnu.org/wiki/GCC_4.3_Release_Planning > > BTW, that page provides a link to "SampleProjectPage" which does not exist. Thanks! I forgot which Wiki syntax I was using; that's now fixed. In order to make life even easier, i renamed the sample project page to end in Template. Now, if you go to create a new page, you can just choose "SampleProjectTemplate" from the list of templates it brings up, and it will start you with a copy of the Sample Project as your wiki page. This way, everybody doesn't have to cut and paste it to start. :)
Re: [gnu.org #304614] Translation of gcc.gnu.org
Hello GCC folks, I'm the coordinator of GNU Chinese translation team. Recently some Chinese volunteers showed their interest in gcc.gnu.org, including the translation of website, document, etc. Before kicking off the translation task, I'd know the following information. 1) Is there already a standard translation process for gcc.gnu.org? 2) Who is the contact point? 3) What kind of document remains high priority in your perspective? 4) Is there a L10N team for GCC? If yes, could we get contact with the team? -- some volunteers also showed the interest in I18N/L10N of GCC. Thanks, -William Leandro Guimarães Faria Corsetti Dutra via RT wrote: As per the footer of the home page, ‘Please send comments on these web pages and the development of GCC to our developer mailing list at [EMAIL PROTECTED]
Re: call dsymutil on darwin when compiling and linking in single step
On 02/09/2006, at 1:10 PM, Jack Howarth wrote: Geoff, Does the patch you propose in... http://gcc.gnu.org/ml/gcc-patches/2006-09/msg00057.html eliminate the "can't find atom for N_GSYM stabs" warnings in ld64? No. It does nothing at all with ld64, or linking in general, and it has no effect if you are using STABS. I ask because you that... This is necessary since otherwise the debugger expects to find the DWARF information in the .o file, but the compiler will have deleted it. ...which makes me wonder if this could be the case. The 'it' refers to the .o file, not the DWARF information. smime.p7s Description: S/MIME cryptographic signature
Re: Many new ICEs in the libstdc++-v3 testsuite
On Fri, 2006-09-01 at 20:13 -0400, Andrew Pinski wrote:
> This was caused by:
> http://gcc.gnu.org/viewcvs?view=rev&revision=116623
And here is one reduced testcase which we just reject now but it is
valid code as far as I can tell:
template< class other>
struct bin_search_tree_data_
{
typedef typename other::node node;
typedef node *node_pointer;
~bin_search_tree_data_()
{
m_p_head->~node();
}
node_pointer m_p_head;
};
struct blowup
{
typedef int node;
};
bin_search_tree_data_< blowup > r;
-- Here is one that ICEs also and closer to
the original code:
template< class other>
struct bin_search_tree_data_
{
typedef typename other::node node;
typedef node *node_pointer;
~bin_search_tree_data_()
{
m_p_head->~node();
}
node_pointer m_p_head;
};
struct blowup2{};
struct blowup
{
typedef blowup2 node;
};
bin_search_tree_data_< blowup > r;
Thanks,
Andrew Pinski
