public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Kenneth Zadeck <zadeck@naturalbridge.com>
To: Andreas Krebbel1 <Andreas.Krebbel@de.ibm.com>
Cc: "Pinski, Andrew" <andrew_pinski@playstation.sony.com>,
	  Serge Belyshev <belyshev@depni.sinp.msu.ru>,
	 "Bonzini, Paolo" <bonzini@gnu.org>,
	  "Berlin, Daniel" <dberlin@dberlin.org>,
	 "Edelsohn, David" <dje@watson.ibm.com>,
	 echristo@apple.com,   gcc-patches <gcc-patches@gcc.gnu.org>,
	 Ian Lance Taylor <iant@google.com>,
	 richard.earnshaw@arm.com,   "Park,
	Seongbae" <seongbae.park@gmail.com>,
	 Steven Bosscher <stevenb.gcc@gmail.com>,
	  Ulrich Weigand <Ulrich.Weigand@de.ibm.com>
Subject: Re: dataflow branch merging plans.
Date: Wed, 30 May 2007 14:17:00 -0000	[thread overview]
Message-ID: <465D7873.7000908@naturalbridge.com> (raw)
In-Reply-To: <OF1A00BB9D.9660DAEC-ONC12572EB.00329667-C12572EB.003320B3@de.ibm.com>

Andreas Krebbel1 wrote:
> Hi,
>
> dataflow branch is clean for s390 and s390x.
>
>   
>> The best way to proceed here is to check out a trunk and then say
>> contrib/gcc_update -r 124834
>>
>> This is the version of the truck that we last merged with and is now a
>> week or so out.  I would be surprised if you have any problems running
>> the regression tests on this version.  Eric Christopher has also had
>> problems with the trunk of later versions than we merged with the mips
>>     
> port.
>   
>> If you do have trouble with 124834, i think that the dataflow branch
>> just has to declare victory, but this is unlikely.  The likely scenario
>> is that it will work and there might be a few regressions.
>>     
>
> I've compared the mainline GCC from the last merge point with a recent
> dataflow checkout:
>
> s390 (31bit) Two ada testcase get fixed with the dataflow branch. No
> regressions otherwise.
>
> < LAST_UPDATED: Tue May 29 13:39:45 UTC 2007 (revision 125162)
> ---
>   
>> LAST_UPDATED: Tue May 29 07:01:10 UTC 2007 (revision 124834)
>>     
> 4a5,6
>   
>> FAIL: c36205l
>> FAIL: cxg2009
>>     
> 22c24
> < /build2/gcc-dataflow-build/gcc/testsuite/g++/../../g++  version 4.3.0
> 20070518 (experimental)
> ---
>   
>> /build2/gcc-4.3-build/gcc/testsuite/g++/../../g++  version 4.3.0 20070518
>>     
> (experimental)
> 31a34,35
>   
>> XPASS: gcc.dg/cpp/cmdlne-dI-M.c scan-file
>>     
> (^|\\\\n)cmdlne-dI-M.*:[^\\\\n]*cmdlne-dI-M.c
>   
>> XPASS: gcc.dg/cpp/cmdlne-dM-M.c scan-file
>>     
> (^|\\\\n)cmdlne-dM-M[^\\\\n]*:[^\\\\n]*cmdlne-dM-M.c
>
>
> s390x (64bit) No regressions at all. The fortran secnds.f testcase still
> behaves indeterministic.
>
> < LAST_UPDATED: Tue May 29 13:39:54 UTC 2007 (revision 125162)
> ---
>   
>> LAST_UPDATED: Tue May 29 07:00:56 UTC 2007 (revision 124834M)
>>     
> 22c22
> < /build2/gcc-dataflow-build/gcc/testsuite/g++/../../g++  version 4.3.0
> 20070518 (experimental)
> ---
>   
>> /build2/gcc-4.3-build/gcc/testsuite/g++/../../g++  version 4.3.0 20070518
>>     
> (experimental)
> 31a32,33
>   
>> XPASS: gcc.dg/cpp/cmdlne-dI-M.c scan-file
>>     
> (^|\\\\n)cmdlne-dI-M.*:[^\\\\n]*cmdlne-dI-M.c
>   
>> XPASS: gcc.dg/cpp/cmdlne-dM-M.c scan-file
>>     
> (^|\\\\n)cmdlne-dM-M[^\\\\n]*:[^\\\\n]*cmdlne-dM-M.c
> ...
> < FAIL: gfortran.dg/secnds.f  -O2  execution test
> ---
>   
>> FAIL: gfortran.dg/secnds.f  -Os  execution test
>>     
>
> Bye,
>
> -Andreas-
>
>   
thanks, this is great news.

  reply	other threads:[~2007-05-30 13:13 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <OF1BD0F1DA.E933CF3F-ON422572E9.006B2EF9-422572E9.006B85BF@de.ibm.com>
2007-05-29  1:05 ` Kenneth Zadeck
2007-05-30 13:11   ` Andreas Krebbel1
2007-05-30 14:17     ` Kenneth Zadeck [this message]
2007-05-25 19:04 Zack Weinberg
     [not found] <OF781E582C.3916D180-ON882572E5.00078CD6-882572E5.00082C95@LocalDomain>
2007-05-25  0:12 ` Andrew_Pinski
  -- strict thread matches above, loose matches on Subject: below --
2007-05-23 13:19 Kenneth Zadeck
2007-05-24  1:29 ` Andrew_Pinski
2007-05-24  7:51   ` Paolo Bonzini
2007-05-24  8:12     ` Paolo Bonzini
2007-05-24 11:47 ` Bernd Schmidt
2007-05-24 20:02   ` Kenneth Zadeck
2007-05-25  9:51     ` Bernd Schmidt
2007-05-25 10:32       ` Paolo Bonzini
2007-05-25 13:00       ` Kenneth Zadeck
2007-05-28 20:55       ` Mark Mitchell
2007-05-29  1:16         ` Kenneth Zadeck
2007-05-29 15:58           ` Mark Mitchell
2007-05-24 21:09   ` Steven Bosscher
2007-05-24 22:23     ` Vladimir N. Makarov
2007-05-24 23:03       ` Steven Bosscher
2007-05-25 13:50         ` Vladimir N. Makarov
2007-05-25 17:15           ` Richard Sandiford
2007-05-25 18:21             ` Jan Hubicka
2007-05-25 20:13             ` Steven Bosscher
2007-05-25 20:11           ` Steven Bosscher

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=465D7873.7000908@naturalbridge.com \
    --to=zadeck@naturalbridge.com \
    --cc=Andreas.Krebbel@de.ibm.com \
    --cc=Ulrich.Weigand@de.ibm.com \
    --cc=andrew_pinski@playstation.sony.com \
    --cc=belyshev@depni.sinp.msu.ru \
    --cc=bonzini@gnu.org \
    --cc=dberlin@dberlin.org \
    --cc=dje@watson.ibm.com \
    --cc=echristo@apple.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=iant@google.com \
    --cc=richard.earnshaw@arm.com \
    --cc=seongbae.park@gmail.com \
    --cc=stevenb.gcc@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).