public inbox for libffi-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Ulderico Cirello <uldericofilho@gmail.com>
To: "Maciej W. Rozycki" <macro@wdc.com>
Cc: gcc-patches@gcc.gnu.org, libffi-discuss@sourceware.org,
		golang-dev <golang-dev@googlegroups.com>
Subject: Re: [golang-dev] [PATCH 0/4] Fix library testsuite compilation for build sysroot
Date: Mon, 11 Nov 2019 18:15:00 -0000	[thread overview]
Message-ID: <CALe9M7m6YhdNqm+wZY9qKbFHQ-o=ePYn9hnC+Lf-+4ZjVWdOTQ@mail.gmail.com> (raw)
In-Reply-To: <alpine.LFD.2.21.1911081714120.13542@redsun52.ssa.fujisawa.hgst.com>

Hi Maciej,


Go's project doesn't take mail patches for changes. Please use gerrit (
https://go-review.googlesource.com/ ).


Thanks





        - ccf


On Mon, Nov 11, 2019 at 10:12 AM Maciej W. Rozycki <macro@wdc.com> wrote:

> Hi,
>
>  This patch series addresses a problem with the testsuite compiler being
> set up across libatomic, libffi, libgo, libgomp with no correlation
> whatsoever to the target compiler being used in GCC compilation.
> Consequently there in no arrangement made to set up the compilation
> sysroot according to the build sysroot specified for GCC compilation,
> causing a catastrophic failure across the testsuites affected from the
> inability to link executables.
>
>  The fix is based on a similar arrangement already made for passing
> autoconf output variables in libgomp, and uses the GCC_UNDER_TEST (or
> GOC_UNDER_TEST, as applicable) TCL variable already used across several
> GCC library testsuites.
>
>  Verified with a cross-compiler configured for the `riscv-linux-gnu'
> target and the `x86_64-linux-gnu' host and using RISC-V/Linux QEMU in the
> user emulation mode as the target board.  Also no change in results with
> `x86_64-linux-gnu' native regression testing.
>
>  See individual change descriptions for details.
>
>  OK to apply to the GCC repo (for libraries maintained externally I'll be
> happy to assist with any merging required, although given that these
> changes are confined to autoconf/automake scriptery they should be
> straightforward to apply, barring any conflicts in generated files)?
>
>   Maciej
>
> --
> You received this message because you are subscribed to the Google Groups
> "golang-dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to golang-dev+unsubscribe@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/golang-dev/alpine.LFD.2.21.1911081714120.13542%40redsun52.ssa.fujisawa.hgst.com
> .
>

  parent reply	other threads:[~2019-11-11 18:15 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-11 18:12 Maciej W. Rozycki
2019-11-11 18:12 ` [PATCH 2/4] libffi/test: Fix " Maciej W. Rozycki
2019-11-11 18:12 ` [PATCH 1/4] libatomic/test: " Maciej W. Rozycki
2019-11-11 18:15 ` Ulderico Cirello [this message]
2019-11-11 18:23   ` [golang-dev] [PATCH 0/4] Fix library testsuite " Kaz Kylheku (libffi)
2019-11-11 18:35     ` Ian Lance Taylor
2019-11-11 18:50       ` Kaz Kylheku (libffi)
2019-11-11 18:33   ` Ian Lance Taylor
2019-11-11 18:44     ` Maciej W. Rozycki
2019-11-11 23:16       ` Ian Lance Taylor
2019-11-11 18:42   ` Maciej W. Rozycki

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='CALe9M7m6YhdNqm+wZY9qKbFHQ-o=ePYn9hnC+Lf-+4ZjVWdOTQ@mail.gmail.com' \
    --to=uldericofilho@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=golang-dev@googlegroups.com \
    --cc=libffi-discuss@sourceware.org \
    --cc=macro@wdc.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).