public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Alexandre Oliva <oliva@adacore.com>
To: David Malcolm <dmalcolm@redhat.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] analyzer: deal with -fshort-enums
Date: Wed, 22 Nov 2023 04:58:55 -0300	[thread overview]
Message-ID: <orsf4ymd6o.fsf@lxoliva.fsfla.org> (raw)
In-Reply-To: <c6daa4f05ff13f29b941efd79cce5ed0336a5788.camel@redhat.com> (David Malcolm's message of "Mon, 20 Nov 2023 17:32:47 -0500")

On Nov 20, 2023, David Malcolm <dmalcolm@redhat.com> wrote:

> On Sun, 2023-11-19 at 04:39 -0300, Alexandre Oliva wrote:
>> 
>> On platforms that enable -fshort-enums by default, various switch-
>> enum
>> analyzer tests fail, because apply_constraints_for_gswitch doesn't
>> expect the integral promotion type cast.  I've arranged for the code
>> to cope with those casts.

> Thanks for the patch, and sorry for the failing tests.

No worries.

> Which tests failed?  I'm guessing one of the ones from r13-5159-
> gccd4df81aa6537.

Yeah, I'm afraid I didn't take notes about which tests failed (I'll try
to dig that up), but I'm sure switch-enum-1, switch-enum-2, and
switch-enum-pr105273-doom-p_maputl.c.  I *think* also switch-enum-5 and
switch-enum-pr105273-doom-p_floor.c.

> Can you add a copy of one of those tests that needs the patch, with an
> explicit -fshort-enums, to ensure that regression testing is hitting
> this case on all targets in the future?

Ah, nice, that's a great idea, I wish I'd thought of that!  Will do.

-- 
Alexandre Oliva, happy hacker            https://FSFLA.org/blogs/lxo/
   Free Software Activist                   GNU Toolchain Engineer
More tolerance and less prejudice are key for inclusion and diversity
Excluding neuro-others for not behaving ""normal"" is *not* inclusive

  reply	other threads:[~2023-11-22  7:59 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-19  7:39 Alexandre Oliva
2023-11-20 22:32 ` David Malcolm
2023-11-22  7:58   ` Alexandre Oliva [this message]
2023-12-06  5:31     ` Alexandre Oliva
2023-12-06 22:22       ` David Malcolm
2024-02-07 16:21         ` Torbjorn SVENSSON
2024-02-22  8:51           ` [PING] " Torbjorn SVENSSON
2024-03-08  9:14             ` [PING^2] " Torbjorn SVENSSON
2024-03-15 10:32               ` [PING^3] " Torbjorn SVENSSON
2024-03-25 14:59                 ` [PING^4] " Yvan ROUX - foss
2024-04-10 13:23                   ` [PING^5] " Torbjorn SVENSSON

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=orsf4ymd6o.fsf@lxoliva.fsfla.org \
    --to=oliva@adacore.com \
    --cc=dmalcolm@redhat.com \
    --cc=gcc-patches@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).