public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "aldyh at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/103161] [12 Regression] Better ranges cause builtin-sprintf-warn-16.c failure
Date: Wed, 10 Nov 2021 16:28:25 +0000	[thread overview]
Message-ID: <bug-103161-4-fSzsXRtlLW@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103161-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #6 from Aldy Hernandez <aldyh at gcc dot gnu.org> ---
(In reply to Martin Sebor from comment #5)
> Great!  With the strlen conversion to ranger
> (g:6b8b959675a3e14cfdd2145bd62e4260eb193765) the test now fails on x86_64 as
> well:

I didn't see any regressions on x86-64 testing, except
builtin-sprintf-warn-22.c which I xfailed.

> I think the test unwittingly depends on GCC not inferring a range from a
> conditional (although the intent is clearly that it does).  It uses an
> unsigned int as the width argument to sprintf which is undefined, but I
> suspect it does it as an attempt to create a signed anti-range.  So this

If the code uses multi-ranges there should be no anti-ranges.  Anti-ranges do
not exist in the new world, and reference to them should be removed.

I still see them in:
gimple-ssa-warn-restrict.c
tree-ssa-strlen.c
builtins.c
ipa-fnsummary.c

(well and in ipa-prop.c, but they're kinda hijacking it for their own
purposes).

The remaining uses are internal to the legacy implementation (vrvalues,
tree-vrp, etc) so they're ok.

  parent reply	other threads:[~2021-11-10 16:28 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-09 16:42 [Bug tree-optimization/103161] New: " law at gcc dot gnu.org
2021-11-09 16:46 ` [Bug tree-optimization/103161] " law at gcc dot gnu.org
2021-11-10  4:26 ` pinskia at gcc dot gnu.org
2021-11-10  4:26 ` pinskia at gcc dot gnu.org
2021-11-10  4:38 ` msebor at gcc dot gnu.org
2021-11-10  7:02 ` aldyh at gcc dot gnu.org
2021-11-10 16:19 ` [Bug testsuite/103161] " msebor at gcc dot gnu.org
2021-11-10 16:28 ` aldyh at gcc dot gnu.org [this message]
2021-11-10 17:14 ` msebor at gcc dot gnu.org
2021-11-10 17:48 ` aldyh at gcc dot gnu.org
2021-11-10 17:49 ` msebor at gcc dot gnu.org
2021-11-10 18:39 ` cvs-commit at gcc dot gnu.org
2021-11-10 18:40 ` msebor 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-103161-4-fSzsXRtlLW@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).