From: Kenneth Zadeck <zadeck@naturalbridge.com>
To: "\"Seongbae Park (???, ???)\"" <seongbae.park@gmail.com>
Cc: gcc-bugzilla@gcc.gnu.org, "Bonzini, Paolo" <bonzini@gnu.org>,
gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [Bug middle-end/32749] [4.3 regression]: gfortran.dg/auto_array_1.f90
Date: Thu, 26 Jul 2007 17:55:00 -0000 [thread overview]
Message-ID: <46A8DB68.9060508@naturalbridge.com> (raw)
In-Reply-To: <ab3a61990707261027o608d0b88k7295d47afd321252@mail.gmail.com>
Seongbae Park (???, ???) wrote:
> On 7/26/07, Kenneth Zadeck <zadeck@naturalbridge.com> wrote:
>> This patch extends the fix in
>> http://gcc.gnu.org/ml/gcc-patches/2007-06/msg01557.html
>> to handle the case of clobbers inside conditional calls.
>>
>> This problem caused the regression of gfortran.dg/matmul_3.f90 on the
>> ia-64 in addition to the regression cited in this pr.
>>
>> Tested on ppc-32, ia-64 and x86-64.
>>
>> 2007-07-26 Kenneth Zadeck <zadeck@naturalbridge.com>
>>
>> PR middle-end/32749
>>
>> * df-problems.c (df_note_bb_compute): Handle case of clobber
>> inside conditional call.
>>
>> ok to commit?
>
> This change is OK.
> Though I wonder if we need to do similar checking
> for the regular insn case below.
No the checking is done in df_create_unused_note. The only reason you
have to do it here is that you are not calling that.
thanks
kenny
next prev parent reply other threads:[~2007-07-26 17:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-32749-682@http.gcc.gnu.org/bugzilla/>
[not found] ` <20070716232625.9422.qmail@sourceware.org>
2007-07-26 12:06 ` Kenneth Zadeck
2007-07-26 17:35 ` Seongbae Park (박성배, 朴成培)
2007-07-26 17:55 ` Kenneth Zadeck [this message]
2007-07-26 18:47 ` Seongbae Park (박성배, 朴成培)
[not found] ` <20070726115131.30046.qmail@sourceware.org>
2007-07-27 17:39 ` Kenneth Zadeck
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=46A8DB68.9060508@naturalbridge.com \
--to=zadeck@naturalbridge.com \
--cc=bonzini@gnu.org \
--cc=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=seongbae.park@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).