public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Hans-Peter Nilsson <hp@axis.com>
To: Bernhard Reutner-Fischer <rep.dot.nop@gmail.com>
Cc: <rep.dot.nop@gmail.com>, <gcc-patches@gcc.gnu.org>,
	<dmalcolm@redhat.com>
Subject: Re: [PATCH 1/2] testsuite: Fix analyzer errors for newlib-errno
Date: Thu, 2 Mar 2023 01:58:57 +0100	[thread overview]
Message-ID: <20230302005857.B6C6F2040C@pchp3.se.axis.com> (raw)
In-Reply-To: <20230302013712.59a001bd@nbbrfq> (message from Bernhard Reutner-Fischer on Thu, 2 Mar 2023 01:37:12 +0100)

> Date: Thu, 2 Mar 2023 01:37:12 +0100
> From: Bernhard Reutner-Fischer <rep.dot.nop@gmail.com>

> On Thu, 2 Mar 2023 00:54:33 +0100
> Hans-Peter Nilsson <hp@axis.com> wrote:
> 
> > > Date: Thu, 2 Mar 2023 00:23:36 +0100
> > > From: Bernhard Reutner-Fischer <rep.dot.nop@gmail.com>  
> > 
> > > On Wed, 1 Mar 2023 17:02:31 +0100
> > > Hans-Peter Nilsson via Gcc-patches <gcc-patches@gcc.gnu.org> wrote:
> > >   
> > > > > From: Hans-Peter Nilsson <hp@axis.com>
> > > > > Date: Wed, 1 Mar 2023 16:36:46 +0100    
> > > >   
> > > > > ... this is what I intend to commit later
> > > > > today, just keeping the added comment as brief as
> > > > > reasonable:    
> > > > 
> > > > Except I see the hook for errno magic took care of
> > > > gcc.dg/analyzer/flex-without-call-summaries.c so I'll add
> > > > that to the list of handled "FAIL"s in the commit log.  Yay.  
> > > 
> > > But in the end it means we'll have to keep _[_]+errno{,_location} 'til
> > > we bump requirements or 10, 20 years or the end of the universe,
> > > doesn't it.
> > > Way fancy.  
> > 
> > Not sure I see your point?  The (other) identifiers are already there.
> 
> I'm certainly not opposed to this partiular identifier, no.
> 
> > 
> > (And you do realize that this is in the analyzer part of gcc, right?)
> 
> And yes, i'm well aware this is "just" the analyzer -- which is unfair
> to state like that and does not mean to imply any inferiority --
> particular in this spot.

(Your statement and values; it can be read as you putting
that as mine, which I hope was not intended.)  My point is
that the presence of those identifiers does not affects an
ABI or code-generating parts of gcc.  All the identifiers
are present for all targets - for all invocation of the
analyzer.  If that passes a nuisance threshold, it seems it
can be changed easily, say by moving it to a target-hook by
someone who cares deeply enough.

> Just let's ditch any specialcased identifier which was superseded
> reliably ASAP?

I'm certainly not opposed to *that*
brgds, H-P

      reply	other threads:[~2023-03-02  0:59 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-28 18:47 Hans-Peter Nilsson
2023-02-28 19:12 ` David Malcolm
2023-03-01  0:59   ` Hans-Peter Nilsson
2023-03-01  2:25     ` David Malcolm
2023-03-01  3:01       ` Hans-Peter Nilsson
2023-03-01 13:32         ` David Malcolm
2023-03-01 15:36           ` Hans-Peter Nilsson
2023-03-01 16:02             ` Hans-Peter Nilsson
2023-03-01 23:23               ` Bernhard Reutner-Fischer
2023-03-01 23:54                 ` Hans-Peter Nilsson
2023-03-02  0:37                   ` Bernhard Reutner-Fischer
2023-03-02  0:58                     ` Hans-Peter Nilsson [this message]

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=20230302005857.B6C6F2040C@pchp3.se.axis.com \
    --to=hp@axis.com \
    --cc=dmalcolm@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=rep.dot.nop@gmail.com \
    /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).