From: Mike Stump <mikestump@comcast.net>
To: Bernhard Reutner-Fischer <rep.dot.nop@gmail.com>
Cc: gcc-patches@gcc.gnu.org, Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
Subject: Re: [PATCH] PR52665 do not let .ident confuse assembler scan tests
Date: Sun, 19 Jun 2016 20:21:00 -0000 [thread overview]
Message-ID: <44774FBA-55E9-4CBB-8EB3-0C67BCC09E62@comcast.net> (raw)
In-Reply-To: <1466278273-7014-1-git-send-email-rep.dot.nop@gmail.com>
On Jun 18, 2016, at 12:31 PM, Bernhard Reutner-Fischer <rep.dot.nop@gmail.com> wrote:
>
> A branch with a name matching scan-assembler pattern triggers
> inappropriate FAIL.
> The patch below adds -fno-ident if a testcase contains one of
> scan-assembler, scan-assembler-not or scan-assembler-times.
Kinda gross. I'd like to consensus build a little, as I don't know that I have a better solution than the solution you propose to fix the issue. I'd love it if one or more of Jacob, Law and Richard can chime in on direction here. I'll have to think about this some more and see if I can come up with something that I like better.
If no one has a better solution, I'll approve the proposed solution. Let's give people a little time to chime in.
next prev parent reply other threads:[~2016-06-19 20:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-18 19:31 Bernhard Reutner-Fischer
2016-06-18 23:49 ` Hans-Peter Nilsson
2016-06-19 20:21 ` Mike Stump [this message]
2018-02-02 13:25 ` Bernhard Reutner-Fischer
2018-02-02 18:56 ` Mike Stump
2018-05-01 17:47 ` Jeff Law
2022-04-25 23:00 ` testsuite -fno-file [was: Re: [PATCH] PR52665 do not let .ident confuse assembler scan tests] Bernhard Reutner-Fischer
2016-06-20 22:20 ` [PATCH] PR52665 do not let .ident confuse assembler scan tests Jeff Law
2018-09-05 15:32 ` Bernhard Reutner-Fischer
2023-05-31 18:50 ` Bernhard Reutner-Fischer
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=44774FBA-55E9-4CBB-8EB3-0C67BCC09E62@comcast.net \
--to=mikestump@comcast.net \
--cc=gcc-patches@gcc.gnu.org \
--cc=rep.dot.nop@gmail.com \
--cc=ro@CeBiTec.Uni-Bielefeld.DE \
/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).