From: "woodard at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: libabigail@sourceware.org
Subject: [Bug default/20194] Fail to recognize void type represented by DW_TAG_base_type
Date: Fri, 01 Jan 2016 00:00:00 -0000 [thread overview]
Message-ID: <bug-20194-9487-oMRbcg1nrZ@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-20194-9487@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=20194
--- Comment #8 from Ben Woodard <woodard at redhat dot com> ---
Much improved!!!
But there still seems to be a much rarer corner case with intel.
13953] subprogram
decl_line (data2) 2594
decl_column (data1) 1
decl_file (data1) 20
type (ref4) [ 505]
prototyped (flag)
name (strp) "malloc_usable_size"
MIPS_linkage_name (strp) "malloc_usable_size"
low_pc (addr) +0x000000000000c1d0
<malloc_usable_size>
high_pc (addr) +0x000000000000c340
<jemalloc_constructor>
external (flag)
[ 13976] formal_parameter
decl_line (data2) 2594
decl_column (data1) 56
decl_file (data1) 20
type (ref4) [ 52f]
name (string) "ptr"
location (block1)
[ 0] reg5
[ 52f] pointer_type
type (ref4) [ 534]
[ 534] const_type
type (ref4) [ 539]
[ 539] base_type
byte_size (data1) 0
encoding (data1) signed (5)
name (strp) "void"
Arguably this is a compiler bug with Intel and that should be considered I
think. There is nothing in the source code that suggests any sort of const-ness
and so the fact that the compiler inserts it here in the type for the parameter
is incorrect.
However, should we consider that to be an ABI relevant artifact?
I can go either way on that. I will be happy to submit a bug to intel regarding
this.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2016-07-05 13:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-01 0:00 [Bug default/20194] New: Intel void* idiom has wrong size woodard at redhat dot com
2016-01-01 0:00 ` woodard at redhat dot com [this message]
2016-01-01 0:00 ` [Bug default/20194] " woodard at redhat dot com
2016-01-01 0:00 ` woodard at redhat dot com
2016-01-01 0:00 ` mjw at redhat dot com
2016-01-01 0:00 ` [Bug default/20194] Fail to recognize void type represented by DW_TAG_base_type dodji at redhat dot com
2016-01-01 0:00 ` [Bug default/20194] Intel void* idiom has wrong size woodard at redhat dot com
2016-01-01 0:00 ` woodard at redhat dot com
2016-01-01 0:00 ` woodard at redhat dot com
2016-01-01 0:00 ` [Bug default/20194] Fail to recognize void type represented by DW_TAG_base_type dodji at redhat dot com
2016-01-01 0:00 ` dodji at redhat dot com
2016-01-01 0:00 ` dodji at redhat dot com
2016-01-01 0:00 ` woodard at redhat dot com
2016-01-01 0:00 ` [Bug default/20194] Intel void* idiom has wrong size woodard 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-20194-9487-oMRbcg1nrZ@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).