public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dnovillo at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/39010] [LTO] Memory corruption on gcc.c-torture/compile/limits-fndefn.c
Date: Sat, 31 Jan 2009 18:49:00 -0000	[thread overview]
Message-ID: <20090131184923.25986.qmail@sourceware.org> (raw)
In-Reply-To: <bug-39010-682@http.gcc.gnu.org/bugzilla/>



------- Comment #5 from dnovillo at gcc dot gnu dot org  2009-01-31 18:49 -------
Subject: Bug 39010

Author: dnovillo
Date: Sat Jan 31 18:49:10 2009
New Revision: 143828

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=143828
Log:

        Revert

        2009-01-30  H.J. Lu  <hongjiu.lu@intel.com>

                PR lto/39010
                * lto-function-out.c (output_string): Properly handle the
                trailing '\0'.
                (output_tree_flags): Updated.


Modified:
    branches/lto/gcc/ChangeLog.lto
    branches/lto/gcc/lto-function-out.c


-- 


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


  parent reply	other threads:[~2009-01-31 18:49 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-28 20:38 [Bug middle-end/39010] New: " hjl dot tools at gmail dot com
2009-01-30 21:09 ` [Bug lto/39010] " hjl dot tools at gmail dot com
2009-01-30 21:22 ` hjl dot tools at gmail dot com
2009-01-30 21:55 ` hjl at gcc dot gnu dot org
2009-01-30 21:58 ` hjl dot tools at gmail dot com
2009-01-31 18:49 ` dnovillo at gcc dot gnu dot org [this message]
2009-01-31 18:51 ` dnovillo at gcc dot gnu dot org
2009-02-17 14:26 ` espindola at gcc dot gnu dot org
2009-07-08  6:07 ` bje at gcc dot gnu dot 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=20090131184923.25986.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).