public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "steven at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/22003] [4.1 Regression] -freorder-blocks-and-partition and thunks
Date: Mon, 01 Aug 2005 00:51:00 -0000	[thread overview]
Message-ID: <20050801005129.13600.qmail@sourceware.org> (raw)
In-Reply-To: <20050610164424.22003.zlynx@acm.org>


------- Additional Comments From steven at gcc dot gnu dot org  2005-08-01 00:51 -------
It was only a sunny smile, 
and little it cost in the giving, 
but like morning light, 
it scattered the night, 
and made the day 
worth living! 
 

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ASSIGNED                    |RESOLVED
         Resolution|                            |FIXED


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


      parent reply	other threads:[~2005-08-01  0:51 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-10 16:44 [Bug c++/22003] New: -freorder-blocks-and-partition causes ICE on 4.1.0 (20050604) zlynx at acm dot org
2005-06-10 16:46 ` [Bug c++/22003] " zlynx at acm dot org
2005-06-10 21:02 ` [Bug c++/22003] [4.1 Regression] -freorder-blocks-and-partition and thunks pinskia at gcc dot gnu dot org
2005-06-28 23:16 ` pinskia at gcc dot gnu dot org
2005-07-27  0:01 ` steven at gcc dot gnu dot org
2005-07-27  1:54 ` steven at gcc dot gnu dot org
2005-07-27 21:05 ` cvs-commit at gcc dot gnu dot org
2005-07-27 21:06 ` steven at gcc dot gnu dot org
2005-07-28 11:46 ` steven at gcc dot gnu dot org
2005-07-29 12:28 ` pinskia at gcc dot gnu dot org
2005-07-31 21:54 ` cvs-commit at gcc dot gnu dot org
2005-08-01  0:51 ` steven at gcc dot gnu dot org [this message]

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=20050801005129.13600.qmail@sourceware.org \
    --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).