Re: 4.3 release plan

2007-05-19 Thread Paolo Bonzini
M 1 - YMMV, YGWYPF, PPINGOFR I got the first two, but what does the last one mean? Wow, you're impressive... The second one I thought would be too cryptic for all. I got the second one too. Italians must be good at acronyms. :-) BTW, the tentative timeline says that 4.3 stage 1 will end

Re: I don't understand some of gcc-4.1-20070514, a patch here.

2007-05-19 Thread J.C. Pizarro
Hi developers, for this http://gcc.gnu.org/ml/gcc/2007-05/msg00451.html you have this nice cleanup's patch of gcc/loop.c that transliterates the logic of the uses of the loop_invariant_p (..) and consec_sets_invariant_p (..) functions. I've patched it, builded and executed, and again again wi

Re: tuples: call for help

2007-05-19 Thread Aldy Hernandez
> >The pretty print routines could definitely use a lot of cases > >(dump_gimple_stmt), and the work is very self contained. > > So I took a look at this the other day, and you seem to have at least > every case that has accessors. > > Did you want me to write accessors for the other types and th

Re: I don't understand some of gcc-4.1-20070514, a patch here.

2007-05-19 Thread Eric Botcazou
> you have this nice cleanup's patch of gcc/loop.c that transliterates the > logic of the uses of the loop_invariant_p (..) and consec_sets_invariant_p > (..) functions. First of all, patches should be posted to gcc-patches@, not to this list. > I've patched it, builded and executed, and again ag

building gcc4-4.3.0-20070518 failed

2007-05-19 Thread Dominique Dhumieres
building snapshot gcc4-4.3.0-2007051 failed with: ... # @multilib_dir@ is not really necessary, but sometimes it has # more uses than just a directory name. /bin/sh ../../../gcc-4.3-20070519/libgcc/../mkinstalldirs . /sw/src/fink.build/gcc4-4.3.0-20070519/darwin_objdir/./gcc/xgcc -B/sw/src

Re: building gcc4-4.3.0-20070518 failed on OSX 10.3.9

2007-05-19 Thread Dominique Dhumieres
Sorry, but I have just realized that I have forgotten to give the OS: OSX 10.3.9, PPC. Also the last week snapshot built without problem. TIA Dominique

Re: I don't understand some of gcc-4.1-20070514, a patch here.

2007-05-19 Thread Manuel López-Ibáñez
J.C., 4.1 is a stable branch. Only patches that fix serious regressions are committed. Thus, your patch cannot be accepted. If your patch is not applicable to 4.3 (which is the current unstable branch) then we are sorry. Please, ask next time before start working in a patch. Cheers, Manuel. P.

Re: I don't understand some of gcc-4.1-20070514, a patch here.

2007-05-19 Thread J.C. Pizarro
2007/5/19, Eric Botcazou <[EMAIL PROTECTED]> wrote: [Please do not cross post between lists and do not send useless attachments.] > I've patched it, builded and executed, and again again with this patched > gcc. It's OK. You apparently didn't read my previous message carefully. The patch is re

Re: I don't understand some of gcc-4.1-20070514, a patch here.

2007-05-19 Thread J.C. Pizarro
2007/5/19, Eric Botcazou <[EMAIL PROTECTED]> wrote: > Eric, what "reason previous stated"? "loop.c is gone in the mainline sources. Patching it on the 4.1 branch is allowed only if you have a testcase that exposes a serious bug." -- Eric Botcazou Yes! There is an serious bug! It's illegible

Re: I don't understand some of gcc-4.1-20070514, a patch here.

2007-05-19 Thread David Daney
J.C. Pizarro wrote: 2007/5/19, Eric Botcazou <[EMAIL PROTECTED]> wrote: > Eric, what "reason previous stated"? "loop.c is gone in the mainline sources. Patching it on the 4.1 branch is allowed only if you have a testcase that exposes a serious bug." -- Eric Botcazou Yes! There is an serio

Re: I don't understand some of gcc-4.1-20070514, a patch here.

2007-05-19 Thread Andrew Pinski
On 5/19/07, J.C. Pizarro <[EMAIL PROTECTED]> wrote: Yes! There is an serious bug! It's illegible, unreadable, illogical, incomprehensible, dirty, heavy, .. And that is the reason why loop.c was removed during 4.2's development. If you don't get that 4.1 is a release branch and is only open fo

Re: I don't understand some of gcc-4.1-20070514, a patch here.

2007-05-19 Thread Gerald Pfeifer
On Sat, 19 May 2007, J.C. Pizarro wrote: > If this message doesn't appear in gcc@gcc.gnu.org and > [EMAIL PROTECTED] as in this subject then > they are censuring me and yours. Please stop this nonsense, and find yourself a different playground from the GCC lists. Gerald

Re: I don't understand some of gcc-4.1-20070514, a patch here.

2007-05-19 Thread Manuel López-Ibáñez
We tried to be polite but I guess that there are actually poisonous people [*] out there. How weird! I truly believed he was just a bit lost/confused. [*] http://video.google.com/videoplay?docid=-4216011961522818645 On 19/05/07, Gerald Pfeifer <[EMAIL PROTECTED]> wrote: On Sat, 19 May 2007,

Re: building gcc4-4.3.0-20070518 failed on OSX 10.3.9

2007-05-19 Thread Dominique Dhumieres
Comparing the log of successful and failed builds I have found that the failed one contains -mdynamic-no-pic which does not appear in the previous build. According Apple's doc this should be used in "application", but it should not appear when building libraries (at least it is my understanding).

Compile Farm Hardware Update: Help Wanted

2007-05-19 Thread Laurent GUERBY
Hi, Our host(1) has asked us to release 5U from our 9U farm, there is no delay for this request but since they have been hosting us freely and reliably for nearly two years I'd like to respond as quickly as possible. FSF France has funding for the purchase of new hardware for up to 10 000 euros (

Re: building gcc4-4.3.0-20070518 failed on OSX 10.3.9

2007-05-19 Thread Andreas Tobler
Dominique Dhumieres wrote: Comparing the log of successful and failed builds I have found that the failed one contains -mdynamic-no-pic which does not appear in the previous build. According Apple's doc this should be used in "application", but it should not appear when building libraries (at l

Re: 4.3 release plan

2007-05-19 Thread Bernardo Innocenti
Paolo Bonzini wrote: >>> I got the first two, but what does the last one mean? >> Wow, you're impressive... The second one I thought would be too cryptic >> for all. > > I got the second one too. Italians must be good at acronyms. :-) IMBGAA! ...BTTOWWTD!!! >>> BTW, the tentative timeline