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 bootstrap/98839] [11 regression] compilation failure for dwarf2asm.c
Date: Tue, 26 Jan 2021 17:14:58 +0000 [thread overview]
Message-ID: <bug-98839-4-e2hVAKikBC@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-98839-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98839
--- Comment #4 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Jakub Jelinek <jakub@gcc.gnu.org>:
https://gcc.gnu.org/g:6e44c09b2df7282e0b519f241cf54438ab183b5e
commit r11-6915-g6e44c09b2df7282e0b519f241cf54438ab183b5e
Author: Jakub Jelinek <jakub@redhat.com>
Date: Tue Jan 26 18:13:07 2021 +0100
dwarf2asm: Fix bootstrap on powerpc*-*-* [PR98839]
My recent dwarf2asm.c patch broke powerpc*-*-* bootstrap, while most target
define POINTER_SIZE to (cond ? cst1 : cst2) or constant, rs6000 defines
it to a variable, and the arbitrarily chosen type of that variable
determines
whether we get warnings on comparison of that against signed or unsigned
ints.
Fixed by adding a cast.
2021-01-26 Jakub Jelinek <jakub@redhat.com>
PR bootstrap/98839
* dwarf2asm.c (dw2_assemble_integer): Cast DWARF2_ADDR_SIZE to int
in comparison.
next prev parent reply other threads:[~2021-01-26 17:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-26 15:19 [Bug bootstrap/98839] New: " seurer at gcc dot gnu.org
2021-01-26 15:21 ` [Bug bootstrap/98839] " seurer at gcc dot gnu.org
2021-01-26 15:38 ` jakub at gcc dot gnu.org
2021-01-26 16:46 ` seurer at gcc dot gnu.org
2021-01-26 17:14 ` cvs-commit at gcc dot gnu.org [this message]
2021-01-27 7:39 ` rguenth at gcc dot gnu.org
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-98839-4-e2hVAKikBC@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: 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).