From: Richard Guenther <richard.guenther@gmail.com>
To: Kai Tietz <ktietz70@googlemail.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>,
"libstdc++" <libstdc++@gcc.gnu.org>,
Jonathan Wakely <jwakely.gcc@gmail.com>
Subject: Re: Ping: Re: [patch middle-end]: Fix PR/48814 - [4.4/4.5/4.6/4.7 Regression] Incorrect scalar increment result
Date: Thu, 15 Mar 2012 15:41:00 -0000 [thread overview]
Message-ID: <CAFiYyc3mcSmKqq6mTvHKvTG6BQomR=ypiu4NA10qTW1HHfAS5w@mail.gmail.com> (raw)
In-Reply-To: <CAEwic4ZG6SvFPTbjpd4Kj5azFNPTVGVANx0NYwmAXvEYT6H4Uw@mail.gmail.com>
On Thu, Mar 15, 2012 at 4:22 PM, Kai Tietz <ktietz70@googlemail.com> wrote:
> Richard,
>
> ping. I think now could be a good time for applying the patch you
> have for this issue as we are in stage 1.
It will still regress the two libstdc++ testcases (well, I guess so at least).
Jonathan - you didn't answer my reply to your question? Would it be ok
to apply this patch with leaving the regressions in-place, to be investigated
by libstdc++ folks?
Thanks,
Richard.
> Regards,
> Kai
next prev parent reply other threads:[~2012-03-15 15:41 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-10 9:59 Kai Tietz
2012-01-10 10:11 ` Richard Guenther
2012-01-10 10:58 ` Kai Tietz
2012-01-11 10:05 ` Richard Guenther
2012-01-11 10:07 ` Richard Guenther
2012-01-11 10:19 ` Kai Tietz
2012-01-11 10:29 ` Richard Guenther
2012-02-08 21:31 ` Kai Tietz
2012-02-09 10:32 ` Richard Guenther
2012-02-09 11:17 ` Richard Guenther
2012-02-09 13:23 ` Richard Guenther
2012-02-09 13:54 ` Kai Tietz
2012-02-09 14:52 ` Richard Guenther
2012-02-09 16:19 ` Richard Guenther
2012-02-10 9:44 ` Kai Tietz
2012-02-10 11:09 ` Richard Guenther
2012-02-10 13:28 ` Jonathan Wakely
2012-02-10 13:31 ` Richard Guenther
2012-02-10 15:20 ` Kai Tietz
2012-03-15 15:22 ` Kai Tietz
2012-03-15 15:41 ` Richard Guenther [this message]
2012-03-16 0:29 ` Jonathan Wakely
2012-03-16 10:11 ` Richard Guenther
2012-03-19 21:43 ` Benjamin De Kosnik
2012-02-10 13:12 ` Andreas Schwab
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='CAFiYyc3mcSmKqq6mTvHKvTG6BQomR=ypiu4NA10qTW1HHfAS5w@mail.gmail.com' \
--to=richard.guenther@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jwakely.gcc@gmail.com \
--cc=ktietz70@googlemail.com \
--cc=libstdc++@gcc.gnu.org \
/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).