public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Hans-Peter Nilsson <hp@bitrange.com>
To: David Malcolm <dmalcolm@redhat.com>
Cc: FX <fxcoudert@gmail.com>, GCC Mailing List <gcc@gcc.gnu.org>,
	 Iain Sandoe <iain@sandoe.co.uk>
Subject: Re: Many analyzer failures on non-Linux system (x86_64-apple-darwin)
Date: Sat, 15 Jan 2022 20:35:40 -0500 (EST)	[thread overview]
Message-ID: <alpine.BSF.2.20.16.2201152017520.13584@arjuna.pair.com> (raw)
In-Reply-To: <c85eb1c5c522d6fad9b08887474258d84882c7bf.camel@redhat.com>

Not seeing anyone doing the obvious one-up, so JFTR:

On Mon, 10 Jan 2022, David Malcolm via Gcc wrote:

> On Mon, 2022-01-10 at 17:13 +0100, FX wrote:
> > > FAIL: gcc.dg/analyzer/asm-x86-lp64-1.c
>
> The purpose of these asm tests is to verify that the analyzer doesn't
> get confused by various inline assembler directives used in the source
> of the Linux kernel.  So in theory they ought to work on any host, with
> a gcc configured for a suitable target.
>
> These tests are marked with "dg-do assemble" directives, which I'd
> hoped would mean it uses -S for the tests (to make a .s file),

No, that's "dg-do compile" (as in "compile but don't assemble").

Also, the default *is* actually "compile" - unless overridden in
an ancestor .exp.  Grep for dg-do-what-default in sibling .exp's
(like dfp/dfp.exp) if you consider changing the default in
analyzer.exp.

brgds, H-P

  parent reply	other threads:[~2022-01-16  1:35 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-23 21:49 FX
2022-01-10 16:13 ` FX
2022-01-10 20:58   ` David Malcolm
2022-01-15 14:19     ` FX
2022-01-15 14:31       ` Iain Sandoe
2022-01-16  1:35     ` Hans-Peter Nilsson [this message]
2022-01-16 11:11       ` FX
2022-01-21  0:08         ` [PATCH] testsuite: avoid analyzer asm failures on non-Linux David Malcolm
2022-02-07 17:08           ` FX
2022-02-07 23:35             ` David Malcolm

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=alpine.BSF.2.20.16.2201152017520.13584@arjuna.pair.com \
    --to=hp@bitrange.com \
    --cc=dmalcolm@redhat.com \
    --cc=fxcoudert@gmail.com \
    --cc=gcc@gcc.gnu.org \
    --cc=iain@sandoe.co.uk \
    /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).