From: Uros Bizjak <ubizjak@gmail.com>
To: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Cc: Jason Merrill <jason@redhat.com>
Subject: Re: C++ PATCH for c++/44282 (ia32 calling convention attributes and mangling)
Date: Tue, 02 Jun 2015 11:52:00 -0000 [thread overview]
Message-ID: <CAFULd4Zh8fHhHrnE0NNd-JMLd5ARzZgbP3PG5U2auzAzuajtww@mail.gmail.com> (raw)
In-Reply-To: <CAFULd4ZYZK6vRK+E+JQK4Z0Goh1dg2aYjRYDP_Cm=fz_+EcSjw@mail.gmail.com>
On Tue, Jun 2, 2015 at 1:03 PM, Uros Bizjak <ubizjak@gmail.com> wrote:
> On Tue, Jun 2, 2015 at 9:26 AM, Uros Bizjak <ubizjak@gmail.com> wrote:
>> Hello!
>>
>>> PR c++/44282
>>> gcc/cp/
>>> * mangle.c (attr_strcmp): New.
>>> (write_CV_qualifiers_for_type): Also write out attributes that
>>> affect type identity.
>>> (write_type): Strip all attributes after writing qualifiers.
>>> libiberty/
>>> * cp-demangle.c (cplus_demangle_type): Handle arguments to vendor
>>> extended qualifier.
>>
>> +++ b/gcc/testsuite/g++.dg/abi/mangle-regparm.C
>> @@ -0,0 +1,29 @@
>> +// { dg-do run { target i?86-*-* } }
>>
>> This should read:
>>
>> +// { dg-do run { target { { i?86-*-* x86_64-*-* } && ia32 } } }
>>
>> The test wasn't actually run on x86_64-linux target. I'll commit the
>> following patch after regtest:
>
> Unfortunately, something is wrong with the testcase itself:
>
> FAIL: g++.dg/abi/mangle-regparm.C -std=c++98 (test for excess errors)
> WARNING: g++.dg/abi/mangle-regparm.C -std=c++98 compilation failed to
> produce executable
> FAIL: g++.dg/abi/mangle-regparm.C -std=c++11 (test for excess errors)
> WARNING: g++.dg/abi/mangle-regparm.C -std=c++11 compilation failed to
> produce executable
> FAIL: g++.dg/abi/mangle-regparm.C -std=c++14 (test for excess errors)
> WARNING: g++.dg/abi/mangle-regparm.C -std=c++14 compilation failed to
> produce executable
>
> with the following error:
>
> FAIL: g++.dg/abi/mangle-regparm.C -std=c++98 (test for excess errors)
> Excess errors:
> /usr/bin/ld: /tmp/ccU8LttY.o: bad reloc symbol index (0x5b550 >= 0x12)
> for offset 0x6c in section `.text'
> /tmp/ccU8LttY.o: could not read symbols: Bad value
>
> WARNING: g++.dg/abi/mangle-regparm.C -std=c++98 compilation failed to
> produce executable
> g++.dg/abi/mangle-regparm.C -std=c++98 : output file does not exist
> UNRESOLVED: g++.dg/abi/mangle-regparm.C -std=c++98 scan-assembler
> _Z18IndirectExternCallIPU7stdcallU7regparmILi3EEFviiEiEvT_T0_S3_
FYI, everything links and runs OK if .set is removed from the
following part of the asm:
.LFE4:
.size _Z18IndirectExternCallIPU7stdcallU7regparmILi3EEFviiEiEvT_T0_S3_,
.-_Z18IndirectExternCallIPU7stdcallU7regparmILi3EEFviiEiEvT_T0_S3_
.weak _Z18IndirectExternCallIPFviiEiEvT_T0_S3_
.set _Z18IndirectExternCallIPFviiEiEvT_T0_S3_,_Z18IndirectExternCallIPU7stdcallU7regparmILi3EEFviiEiEvT_T0_S3_
.section
.text._Z18IndirectExternCallIPFviiEiEvT_T0_S3_,"axG",@progbits,_Z18IndirectExternCallIPFviiEiEvT_T0_S3_,comdat
.weak _Z18IndirectExternCallIPFviiEiEvT_T0_S3_
.type _Z18IndirectExternCallIPFviiEiEvT_T0_S3_, @function
_Z18IndirectExternCallIPFviiEiEvT_T0_S3_:
Uros.
next prev parent reply other threads:[~2015-06-02 11:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-02 7:31 Uros Bizjak
2015-06-02 11:07 ` Uros Bizjak
2015-06-02 11:52 ` Uros Bizjak [this message]
2015-06-02 13:11 ` Jason Merrill
2015-06-03 21:39 ` Jason Merrill
2015-09-14 17:41 ` Jason Merrill
-- strict thread matches above, loose matches on Subject: below --
2015-06-02 2:55 Jason Merrill
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=CAFULd4Zh8fHhHrnE0NNd-JMLd5ARzZgbP3PG5U2auzAzuajtww@mail.gmail.com \
--to=ubizjak@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jason@redhat.com \
/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).