From: "dodji at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: libabigail@sourceware.org
Subject: [Bug default/20420] Wrong ODR-based type comparison optimization on qualified type
Date: Fri, 01 Jan 2016 00:00:00 -0000 [thread overview]
Message-ID: <bug-20420-9487-NakEIOSIVS@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-20420-9487@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=20420
--- Comment #2 from dodji at redhat dot com ---
(In reply to dodji from comment #1)
> Basically, a const anonymous struct (a qualified type)
> from the second ABI corpus is wrongly being considered equivalent
> to another (different) const anonymous struct from the first ABI corpus.
Sorry, this should rather be:
Basically, a const anonymous struct (a qualified type)
from the second ABI corpus is wrongly being considered equivalent
to another (different) const anonymous struct from that same corpus.
Of course the first corpus and the second corpus happen to be identical in the
particular test case of this problem report, but I think the underlying problem
exists independently from that fact.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2016-08-24 8:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-01 0:00 [Bug default/20420] New: abipkgdiff aborted((core dumped)) while running on glibc package sinny at redhat dot com
2016-01-01 0:00 ` [Bug default/20420] Wrong ODR-based type comparison optimization on qualified type dodji at redhat dot com
2016-01-01 0:00 ` dodji at redhat dot com [this message]
2016-01-01 0:00 ` dodji at redhat 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-20420-9487-NakEIOSIVS@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=libabigail@sourceware.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).