Re: No .got section in ELF

2009-11-29 Thread Yunfeng ZHANG
Thank you! I've known to how to create a *compat* PIC library, firstly using `-fvisibility=hidden' in compile command line to hidden all symbols, then using `objcopy -R' to remove .got section totally! However, assemble result is just like this call__i686.get_pc_thunk.bx addl

Re: Caused by unknown alignment, was: Re: On the x86_64, does one have to zero a vector register before filling it completely ?

2009-11-29 Thread Steven Bosscher
On Mon, Nov 30, 2009 at 12:40 AM, Daniel Berlin wrote: > This pass may even be on the lno branch or something. It used to be, at least, see http://gcc.gnu.org/ml/gcc-cvs/2004-08/msg00470.html Happy hacking, Toon :-) Ciao! Steven

MPC required in one week.

2009-11-29 Thread Kaveh R. GHAZI
The patch which makes the MPC library a hard requirement for GCC bootstrapping has been approved today. As promised, I'll wait one week before applying it to give everyone a chance to install MPC on their systems. You can download mpc-0.8 from either of these two locations: ftp://gcc.gnu.org/pub/

Re: Caused by unknown alignment, was: Re: On the x86_64, does one have to zero a vector register before filling it completely ?

2009-11-29 Thread Daniel Berlin
On Sun, Nov 29, 2009 at 3:33 PM, Richard Guenther wrote: > On Sun, Nov 29, 2009 at 9:18 PM, Daniel Berlin wrote: >>> >>> Such a thing already existed a few years ago (IIRC Haifa had something >>> that Dan picked up and passed on to me). But it never brought any >>> benefits. I don't have the pass

gcc-4.3-20091129 is now available

2009-11-29 Thread gccadmin
Snapshot gcc-4.3-20091129 is now available on ftp://gcc.gnu.org/pub/gcc/snapshots/4.3-20091129/ and on various mirrors, see http://gcc.gnu.org/mirrors.html for details. This snapshot has been generated from the GCC 4.3 SVN branch with the following options: svn://gcc.gnu.org/svn/gcc/branches

plugin issues to fix (or document) before 4.5 release

2009-11-29 Thread Basile STARYNKEVITCH
Hello All, I believe there are several plugin issues to fix before 4.5 releases: 1. use of libiberty from plugins. As several patches recently sent demonstrated, the current state of the trunk does not work with plugins calling some of the libiberty functions is IMHO not acceptable. we c

Re: Caused by unknown alignment, was: Re: On the x86_64, does one have to zero a vector register before filling it completely ?

2009-11-29 Thread Richard Guenther
On Sun, Nov 29, 2009 at 9:18 PM, Daniel Berlin wrote: >> >> Such a thing already existed a few years ago (IIRC Haifa had something >> that Dan picked up and passed on to me). But it never brought any >> benefits. I don't have the pass anymore, but perhaps Dan still has a >> copy of it somewhere. >

Re: Caused by unknown alignment, was: Re: On the x86_64, does one have to zero a vector register before filling it completely ?

2009-11-29 Thread Daniel Berlin
> > Such a thing already existed a few years ago (IIRC Haifa had something > that Dan picked up and passed on to me). But it never brought any > benefits. I don't have the pass anymore, but perhaps Dan still has a > copy of it somewhere. It was actually posted and reviewed, you can find it in the

Re: Caused by unknown alignment, was: Re: On the x86_64, does one have to zero a vector register before filling it completely ?

2009-11-29 Thread Steven Bosscher
On Sun, Nov 29, 2009 at 7:12 PM, Toon Moene wrote: > Toon Moene wrote: > >> This is where IPA could help.  I created the following main program: >> >>      real a(10), b(10), c(10) >>      a = 0. >>      b = 1. >>      print '(3(1x,z16))', loc(a), loc(b), loc(c) >>      call sum(a, b, c, 10) >>  

Re: Caused by unknown alignment, was: Re: On the x86_64, does one have to zero a vector register before filling it completely ?

2009-11-29 Thread Toon Moene
Toon Moene wrote: This is where IPA could help. I created the following main program: real a(10), b(10), c(10) a = 0. b = 1. print '(3(1x,z16))', loc(a), loc(b), loc(c) call sum(a, b, c, 10) print *, c(5) end So the alignment of a, b and c is known a

Re: Reminder: Stage3 ends Nov 30th

2009-11-29 Thread Dave Korn
Richard Guenther wrote: > We'll be all reasonable folks. Please don't again open another > huge thread with "*random whine*, please consider my patch!". There is a finite amount of time and a finite number of reviewers, and a random number of outstanding patches. Wouldn't a handy list of them

Re: Two corrupted libstdc++-v3 files in gcc-4.4.2.tar.gz (invalid file extension)

2009-11-29 Thread Nicolai Josuttis
Ah, interesting. well the point is that I extracted the files with WinZip (Version 9.0, build 6028) before I started the built in a cygwin environment. So, it's not a cygwin, it's a WinZip bug (I can confirm that cygwin tar extracts the files with the correct extension). Thanks for the fast feed

Re: Reminder: Stage3 ends Nov 30th

2009-11-29 Thread Richard Guenther
On Sun, 29 Nov 2009, Kaveh R. GHAZI wrote: > On Sun, 29 Nov 2009, Richard Guenther wrote: > > > > > This is a remainder to not catch you in surprise when we announce > > the end of stage 3. Starting Dec 1st the trunk will go into > > regression and documentation fixes only mode (thus, same rules

Re: Reminder: Stage3 ends Nov 30th

2009-11-29 Thread Kaveh R. GHAZI
On Sun, 29 Nov 2009, Richard Guenther wrote: > > This is a remainder to not catch you in surprise when we announce > the end of stage 3. Starting Dec 1st the trunk will go into > regression and documentation fixes only mode (thus, same rules > apply as for a release branch). When the release cri

Re: Reminder: Stage3 ends Nov 30th

2009-11-29 Thread Dave Korn
Richard Guenther wrote: > This is a remainder to not catch you in surprise when we announce > the end of stage 3. Starting Dec 1st the trunk will go into > regression and documentation fixes only mode Is there perhaps a nice, noble, brave, honest, handsome, heroic, sweetly-smelling driver or g

Re: Two corrupted libstdc++-v3 files in gcc-4.4.2.tar.gz (invalid file extension)

2009-11-29 Thread Richard Guenther
On Sun, Nov 29, 2009 at 3:07 PM, Nicolai Josuttis wrote: > Hi everybody, > > I am currently starting to work on a new edition of my > C++ Library book and from what I see, you already have > good support of a couple of new feature. Great! > So, I start to try g++ 4.4.2 out now... > > However, both

Re: i370 port - music/sp - possible generic gcc problem

2009-11-29 Thread Paul Edwards
Latest information - Ok, based on this, I traced it back further: rtx gen_rtx_fmt_e0 (code, mode, arg0) RTX_CODE code; enum machine_mode mode; rtx arg0; { rtx rt; rt = ggc_alloc_rtx (2); memset (rt, 0, sizeof (struct rtx_def) - sizeof (rtunion)); The request for 2 (I guess, rtx

Caused by unknown alignment, was: Re: On the x86_64, does one have to zero a vector register before filling it completely ?

2009-11-29 Thread Toon Moene
Toon Moene wrote: Tim Prince wrote: > If you want those, you must request them with -mtune=barcelona. OK, so it is an alignment issue (with -mtune=barcelona): .L6: movups 0(%rbp,%rax), %xmm0 movups (%rbx,%rax), %xmm1 incl%ecx addps %xmm1, %xmm0

Two corrupted libstdc++-v3 files in gcc-4.4.2.tar.gz (invalid file extension)

2009-11-29 Thread Nicolai Josuttis
Hi everybody, I am currently starting to work on a new edition of my C++ Library book and from what I see, you already have good support of a couple of new feature. Great! So, I start to try g++ 4.4.2 out now... However, both gcc-g++-4.4.2.tar.gz as well as gcc-4.4.2.tar.gz downloaded from mul

Induction variable elimination, was: Re: On the x86_64, does one have to zero a vector register before filling it completely ?

2009-11-29 Thread Toon Moene
Toon Moene wrote: I wrote: OK, so it is an alignment issue (with -mtune=barcelona): .L6: movups 0(%rbp,%rax), %xmm0 movups (%rbx,%rax), %xmm1 incl%ecx addps %xmm1, %xmm0 movaps %xmm0, (%r8,%rax) addq$16, %rax cmpl%r10d,

Reminder: Stage3 ends Nov 30th

2009-11-29 Thread Richard Guenther
This is a remainder to not catch you in surprise when we announce the end of stage 3. Starting Dec 1st the trunk will go into regression and documentation fixes only mode (thus, same rules apply as for a release branch). When the release criteria are fulfilled (mainly zero P1 regressions) we wil