public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Uros Bizjak <uros@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc r13-7791] i386: Handle CONST_WIDE_INT in output_pic_addr_const [PR111340] Date: Mon, 11 Sep 2023 21:47:48 +0000 (GMT) [thread overview] Message-ID: <20230911214748.8575C3858D3C@sourceware.org> (raw) https://gcc.gnu.org/g:65331a30922887304c183be4686ddaf12e990c6b commit r13-7791-g65331a30922887304c183be4686ddaf12e990c6b Author: Uros Bizjak <ubizjak@gmail.com> Date: Mon Sep 11 20:56:42 2023 +0200 i386: Handle CONST_WIDE_INT in output_pic_addr_const [PR111340] PR target/111340 gcc/ChangeLog: * config/i386/i386.cc (output_pic_addr_const): Handle CONST_WIDE_INT. Call output_addr_const for CASE_CONST_SCALAR_INT. gcc/testsuite/ChangeLog: * gcc.target/i386/pr111340.c: New test. Diff: --- gcc/config/i386/i386.cc | 4 ++-- gcc/testsuite/gcc.target/i386/pr111340.c | 9 +++++++++ 2 files changed, 11 insertions(+), 2 deletions(-) diff --git a/gcc/config/i386/i386.cc b/gcc/config/i386/i386.cc index 261fd00f3ad2..2176de57b72f 100644 --- a/gcc/config/i386/i386.cc +++ b/gcc/config/i386/i386.cc @@ -12302,8 +12302,8 @@ output_pic_addr_const (FILE *file, rtx x, int code) assemble_name (asm_out_file, buf); break; - case CONST_INT: - fprintf (file, HOST_WIDE_INT_PRINT_DEC, INTVAL (x)); + CASE_CONST_SCALAR_INT: + output_addr_const (file, x); break; case CONST: diff --git a/gcc/testsuite/gcc.target/i386/pr111340.c b/gcc/testsuite/gcc.target/i386/pr111340.c new file mode 100644 index 000000000000..6539ae566c03 --- /dev/null +++ b/gcc/testsuite/gcc.target/i386/pr111340.c @@ -0,0 +1,9 @@ +/* PR target/111340 */ +/* { dg-do compile { target { fpic && int128 } } } */ +/* { dg-options "-O2 -fpic" } */ + +void +bar (void) +{ + __asm ("# %0" : : "g" ((((unsigned __int128) 0x123456789abcdef0ULL) << 64) | 0x0fedcba987654321ULL)); +}
reply other threads:[~2023-09-11 21:47 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20230911214748.8575C3858D3C@sourceware.org \ --to=uros@gcc.gnu.org \ --cc=gcc-cvs@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).