public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ebotcazou at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/55030] [4.8 Regression]: gcc.c-torture/execute/builtins/memcpy-chk.c execution,  -Os (et al)
Date: Sat, 16 Feb 2013 09:44:00 -0000	[thread overview]
Message-ID: <bug-55030-4-JaDr2EwiMG@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-55030-4@http.gcc.gnu.org/bugzilla/>


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55030

--- Comment #11 from Eric Botcazou <ebotcazou at gcc dot gnu.org> 2013-02-16 09:44:31 UTC ---
While we are at it, we could also revert the dse.c and cselib.c hunks of the
blockage patch, which weren't strictly necessary.  Jakub was really concerned
about their impact on volatile asms.


  parent reply	other threads:[~2013-02-16  9:44 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-23  0:58 [Bug middle-end/55030] New: " hp at gcc dot gnu.org
2012-10-23  1:05 ` [Bug middle-end/55030] " hp at gcc dot gnu.org
2012-10-23  1:08 ` hp at gcc dot gnu.org
2012-10-23  1:09 ` hp at gcc dot gnu.org
2012-10-23  9:39 ` rguenth at gcc dot gnu.org
2012-11-12  4:37 ` hp at gcc dot gnu.org
2012-11-12  4:54 ` hp at gcc dot gnu.org
2012-11-26  3:22 ` hp at gcc dot gnu.org
2012-11-26  3:26 ` hp at gcc dot gnu.org
2012-11-27  7:41 ` krebbel at gcc dot gnu.org
2012-11-27 11:55 ` hp at gcc dot gnu.org
2012-11-27 23:16 ` hp at gcc dot gnu.org
2013-02-16  9:37 ` ebotcazou at gcc dot gnu.org
2013-02-16  9:44 ` ebotcazou at gcc dot gnu.org [this message]
2013-02-17  0:33 ` hp at gcc dot gnu.org
2013-02-18 10:48 ` ebotcazou at gcc dot gnu.org
2013-02-18 22:21 ` hp at gcc dot gnu.org
2013-02-19 11:32 ` ebotcazou at gcc dot gnu.org
2013-06-03  8:37 ` mikpe at it dot uu.se
2013-06-03 22:32 ` hp at gcc dot gnu.org
2013-06-08  7:50 ` ebotcazou at gcc dot gnu.org
2013-07-03 14:44 ` hp at gcc dot gnu.org

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=bug-55030-4-JaDr2EwiMG@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).