From: Dominik Vogt <vogt@linux.vnet.ibm.com>
To: gcc-patches <gcc-patches@gcc.gnu.org>,
"gofrontend-dev@googlegroups.com"
<gofrontend-dev@googlegroups.com>
Cc: Ian Taylor <iant@golang.org>
Subject: Re: [gofrontend-dev] [PATCH 4/4] Gccgo port to s390[x] -- part II
Date: Mon, 10 Nov 2014 14:24:00 -0000 [thread overview]
Message-ID: <20141110140004.GA515@linux.vnet.ibm.com> (raw)
In-Reply-To: <CAOyqgcVnPkBOtKYD8rF48RYXQ-5u_i7ZN9OftsAMUE8rYR1uCA@mail.gmail.com>
> I'd still like to avoid the rampant duplication if possible. One
> approach would be to put most of the test in something like
> nilptr_tests.go marked with "// skip". Then we can have top-level
> nilptrXX.go tests with +build lines that use "// run nilptr_tests.go".
I fail to see how that could be done with "// run". There is one
example use, namely cmplxdivide.go". That is not run in gcc
because the "run" line does not match anything in go-test.exp. If
I add a rule for that, how does that help me to compile a test
that consists of multiple files?
At the moment, I've no idea how to tackle the multi file problem
with the existing go-test.exp.
Ciao
Dominik ^_^ ^_^
--
Dominik Vogt
IBM Germany
next prev parent reply other threads:[~2014-11-10 14:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-04 12:16 Dominik Vogt
2014-11-05 4:16 ` [gofrontend-dev] " Ian Taylor
2014-11-05 10:05 ` Dominik Vogt
2014-11-05 15:52 ` Ian Taylor
2014-11-06 12:04 ` Dominik Vogt
2014-11-06 17:06 ` Ian Taylor
2014-11-07 8:51 ` Dominik Vogt
2014-11-07 16:24 ` Ian Taylor
2014-11-13 10:59 ` Dominik Vogt
2014-11-15 16:23 ` Ian Taylor
2014-11-18 7:53 ` Dominik Vogt
2014-11-10 14:24 ` Dominik Vogt [this message]
2014-11-10 16:18 ` Ian Taylor
2014-11-09 21:16 ` Michael Hudson-Doyle
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=20141110140004.GA515@linux.vnet.ibm.com \
--to=vogt@linux.vnet.ibm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gofrontend-dev@googlegroups.com \
--cc=iant@golang.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).