public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dmalcolm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug analyzer/110483] [14 Regression] Several gcc.dg/analyzer/out-of-bounds-diagram-*.c tests FAIL
Date: Thu, 29 Feb 2024 16:08:18 +0000	[thread overview]
Message-ID: <bug-110483-4-UI6yeXKtm4@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-110483-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110483

--- Comment #6 from David Malcolm <dmalcolm at gcc dot gnu.org> ---
Thanks; let's keep using this PR for the stuff in comment #5.

I've been looking at these on gcc211 in the compile farm:
  * I see out-of-bounds-diagram-11.c failing as you describe (the overflow in
test6 isn't reported with g++ for some reason; it is for gcc)
  * out-of-bounds-diagram-3.c gets skipped on that machine due to 
    { dg-require-effective-target lp64 }
    "check_cached_effective_target lp64: returning 0 for unix"

Is there a config/cfarm machine you see the out-of-bounds-diagram-3.c failure
on?

  parent reply	other threads:[~2024-02-29 16:08 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-29 11:09 [Bug analyzer/110483] New: " ro at gcc dot gnu.org
2023-06-29 11:10 ` [Bug analyzer/110483] " ro at gcc dot gnu.org
2023-06-29 20:22 ` dmalcolm at gcc dot gnu.org
2023-06-30 12:59 ` ro at CeBiTec dot Uni-Bielefeld.DE
2024-02-27 22:19 ` [Bug analyzer/110483] [14 Regression] " cvs-commit at gcc dot gnu.org
2024-02-27 22:29 ` dmalcolm at gcc dot gnu.org
2024-02-29 10:30 ` ro at gcc dot gnu.org
2024-02-29 16:08 ` dmalcolm at gcc dot gnu.org [this message]
2024-02-29 20:37 ` ro at CeBiTec dot Uni-Bielefeld.DE
2024-05-07  7:40 ` [Bug analyzer/110483] [14/15 " 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-110483-4-UI6yeXKtm4@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).