public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ramana at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/53664] neon-testgen.ml generates duplicate scan-assembler directives
Date: Mon, 30 Jul 2012 18:31:00 -0000 [thread overview]
Message-ID: <bug-53664-4-EqEcSlKG9A@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-53664-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53664
--- Comment #4 from Ramana Radhakrishnan <ramana at gcc dot gnu.org> 2012-07-30 18:30:40 UTC ---
(In reply to comment #0)
> Tests gcc/testsuite/gcc.target/arm/neon/v*.c are generated by the script
> gcc/config/arm/neon-testgen.ml. 54 of these tests have duplicate
> scan-assembler test directives, leading to duplicate lines in the test summary
> file. The test generator is an O'Caml program.
>
> I'm hoping that someone who knows that language will kindly take a look at this
> bug, fix it, and regenerate the tests.
I took a quick peek , it's a bit of work to get this done - the problem really
is in the way in which we are generating with emit_epilogue - would be nice if
one could get a hold of VecArray at this point of time and generate
scan-assembler-times the arity ....
I don't do enough ML to deal with it right now.
Ramana
next prev parent reply other threads:[~2012-07-30 18:31 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-14 0:03 [Bug testsuite/53664] New: " janis at gcc dot gnu.org
2012-06-20 10:17 ` [Bug testsuite/53664] " ramana at gcc dot gnu.org
2012-06-20 14:16 ` janis at gcc dot gnu.org
2012-06-20 15:00 ` ramana at gcc dot gnu.org
2012-07-30 18:31 ` ramana at gcc dot gnu.org [this message]
2012-07-30 18:35 ` janis at gcc dot gnu.org
2012-07-31 0:01 ` ramana at gcc dot gnu.org
2012-07-31 0:05 ` ramana at gcc dot gnu.org
2012-07-31 15:56 ` janis at gcc dot gnu.org
2012-07-31 16:17 ` ramana at gcc dot gnu.org
2012-07-31 16:50 ` janis at gcc dot gnu.org
2012-07-31 17:31 ` janis at gcc dot gnu.org
2012-07-31 17:57 ` ramana at gcc dot gnu.org
2012-07-31 18:02 ` janis at gcc dot gnu.org
2012-08-01 23:36 ` janis at gcc dot gnu.org
2012-08-02 10:11 ` ramrad01 at arm dot com
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-53664-4-EqEcSlKG9A@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).