public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/56344] ICE for program with very large structs returned by value
Date: Fri, 22 Mar 2013 14:48:00 -0000	[thread overview]
Message-ID: <bug-56344-4-N6dRxoC8JC@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-56344-4@http.gcc.gnu.org/bugzilla/>


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

Jakub Jelinek <jakub at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Target Milestone|4.8.0                       |4.8.1

--- Comment #6 from Jakub Jelinek <jakub at gcc dot gnu.org> 2013-03-22 14:45:18 UTC ---
GCC 4.8.0 is being released, adjusting target milestone.


  parent reply	other threads:[~2013-03-22 14:46 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-15 15:04 [Bug c/56344] New: ICE for program with larger automatic structs georggcc at googlemail dot com
2013-02-15 15:16 ` [Bug c/56344] " georggcc at googlemail dot com
2013-02-18 11:16 ` [Bug middle-end/56344] ICE for program with very large structs returned by value rguenth at gcc dot gnu.org
2013-02-22 14:28 ` mpolacek at gcc dot gnu.org
2013-02-22 14:34 ` mpolacek at gcc dot gnu.org
2013-02-26 18:29 ` mpolacek at gcc dot gnu.org
2013-03-22 14:48 ` jakub at gcc dot gnu.org [this message]
2013-05-31 10:59 ` jakub at gcc dot gnu.org
2013-10-16  9:51 ` jakub at gcc dot gnu.org
2013-12-03 12:11 ` mpolacek at gcc dot gnu.org
2013-12-03 12:41 ` mpolacek at gcc dot gnu.org
2014-01-13 17:21 ` georggcc at googlemail dot com

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-56344-4-N6dRxoC8JC@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).