public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "bje at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug lto/39279] [lto] - Werror in ../lto_trunk/gcc/lto/lto.c Date: Wed, 15 Jul 2009 00:49:00 -0000 [thread overview] Message-ID: <20090715004938.23431.qmail@sourceware.org> (raw) In-Reply-To: <bug-39279-13830@http.gcc.gnu.org/bugzilla/> ------- Comment #3 from bje at gcc dot gnu dot org 2009-07-15 00:49 ------- Fixed by this patch: 2009-07-09 Rainer Orth <ro@TechFak.Uni-Bielefeld.DE> * lto.c (free_section_data): Cast computed_offset to caddr_t. I felt this was not the right fix, but I won't argue. -- bje at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39279
next prev parent reply other threads:[~2009-07-15 0:49 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-02-23 19:07 [Bug bootstrap/39279] New: " rob1weld at aol dot com 2009-03-09 6:40 ` [Bug lto/39279] " rob1weld at aol dot com 2009-07-09 0:14 ` bje at gcc dot gnu dot org 2009-07-15 0:49 ` bje at gcc dot gnu dot org [this message] 2009-07-17 6:44 ` rob1weld at aol 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=20090715004938.23431.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: linkBe 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).