public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/111340] gcc.dg/bitint-12.c fails on x86_64-apple-darwin or fails on x86_64-linux-gnu with -fPIE Date: Mon, 11 Sep 2023 21:47:49 +0000 [thread overview] Message-ID: <bug-111340-4-EIaBCCbpko@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-111340-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111340 --- Comment #8 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-13 branch has been updated by Uros Bizjak <uros@gcc.gnu.org>: 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.
next prev parent reply other threads:[~2023-09-11 21:47 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-09-08 15:14 [Bug c/111340] New: gcc.dg/bitint-12.c fails on x86_64-apple-darwin fxcoudert at gcc dot gnu.org 2023-09-08 15:23 ` [Bug target/111340] " pinskia at gcc dot gnu.org 2023-09-08 15:24 ` fxcoudert at gcc dot gnu.org 2023-09-08 15:47 ` [Bug target/111340] gcc.dg/bitint-12.c fails on x86_64-apple-darwin or fails on x86_64-linux-gnu with -fPIE jakub at gcc dot gnu.org 2023-09-08 16:02 ` jakub at gcc dot gnu.org 2023-09-11 6:55 ` ubizjak at gmail dot com 2023-09-11 6:58 ` jakub at gcc dot gnu.org 2023-09-11 18:57 ` cvs-commit at gcc dot gnu.org 2023-09-11 21:47 ` cvs-commit at gcc dot gnu.org [this message] 2023-09-12 16:03 ` cvs-commit at gcc dot gnu.org 2023-09-12 21:11 ` cvs-commit at gcc dot gnu.org 2023-09-12 21:12 ` ubizjak at gmail 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-111340-4-EIaBCCbpko@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: 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).