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 tree-optimization/64330] [5 Regression] IPA-ICF merges const exported vars that could be addressable in other TUs
Date: Tue, 16 Dec 2014 18:09:00 -0000	[thread overview]
Message-ID: <bug-64330-4-EfScCBAgmS@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-64330-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64330

--- Comment #5 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
(In reply to Kostya Serebryany from comment #4)
> So, maybe the ODR checker in the current form is not that useless.
> Sorry, couldn't resist :)

But it isn't really an ODR checker.  Here it complains if two different symbols
share the same storage.  Which is fine if they aren't address taken and can't
be address taken elsewhere.


  parent reply	other threads:[~2014-12-16 18:09 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-16 12:34 [Bug sanitizer/64330] New: [ASAN] Bogus "AddressSanitizer: odr-violation" burnus at gcc dot gnu.org
2014-12-16 12:45 ` [Bug sanitizer/64330] " trippels at gcc dot gnu.org
2014-12-16 13:43 ` jakub at gcc dot gnu.org
2014-12-16 14:02 ` [Bug tree-optimization/64330] [5 Regression] IPA-ICF merges const exported vars that could be addressable in other TUs jakub at gcc dot gnu.org
2014-12-16 18:01 ` kcc at gcc dot gnu.org
2014-12-16 18:09 ` jakub at gcc dot gnu.org [this message]
2014-12-17 14:30 ` y.gribov at samsung dot com
2014-12-17 16:49 ` hubicka at gcc dot gnu.org
2014-12-17 19:08 ` hubicka at ucw dot cz
2014-12-18 13:32 ` marxin 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-64330-4-EfScCBAgmS@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).