public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "mark at klomp dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug compile/29198] [Regression] specified bound 4294967295 may exceed maximum object size 2147483647
Date: Tue, 31 May 2022 09:06:23 +0000 [thread overview]
Message-ID: <bug-29198-4717-UUugQhkN5f@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29198-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=29198
Mark Wielaard <mark at klomp dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
See Also| |https://gcc.gnu.org/bugzill
| |a/show_bug.cgi?id=97185
--- Comment #3 from Mark Wielaard <mark at klomp dot org> ---
(In reply to John David Anglin from comment #2)
> Might this be a gcc bug?
Yes, I suspect it is https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97185 where
some range information is removed for some, but not all builtins causing the
impossible warning message about the string size.
I proposed the following patch to just always suppress this diagnostic for now
on all arches:
https://sourceware.org/pipermail/gdb-patches/2022-May/189603.html
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2022-05-31 9:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-30 19:11 [Bug compile/29198] New: " danglin at gcc dot gnu.org
2022-05-30 19:27 ` [Bug compile/29198] " mark at klomp dot org
2022-05-30 22:39 ` danglin at gcc dot gnu.org
2022-05-31 9:06 ` mark at klomp dot org [this message]
2022-06-06 13:31 ` [Bug build/29198] " tromey at sourceware dot org
2022-12-23 20:04 ` tromey at sourceware dot org
2022-12-23 21:26 ` dave.anglin at bell dot net
2022-12-23 21:42 ` mark at klomp dot org
2022-12-24 1:56 ` tromey at sourceware dot org
2022-12-24 10:43 ` mark at klomp dot 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-29198-4717-UUugQhkN5f@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=gdb-prs@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).