All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bastian Koppelmann <kbastian@mail.uni-paderborn.de>
To: "Alex Bennée" <alex.bennee@linaro.org>,
	"QEMU Developers" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [RFC PATCH 02/12] tests/tcg/tricore: Add build infrastructure
Date: Wed, 2 May 2018 11:42:50 +0200	[thread overview]
Message-ID: <583cb654-2e10-14e2-faed-36c52a2f306a@mail.uni-paderborn.de> (raw)
In-Reply-To: <f24f7977-cd8b-f502-e3f1-2ae6b0f422d8@mail.uni-paderborn.de>

On 05/01/2018 06:48 PM, Bastian Koppelmann wrote:
> Hi Alex,
> 
> On 05/01/2018 05:40 PM, Alex Bennée wrote:
>> Bastian Koppelmann <kbastian@mail.uni-paderborn.de> writes:
>>
>>> this includes the Makefile and linker script to build all the tests.
>>>
>>> Signed-off-by: Bastian Koppelmann <kbastian@mail.uni-paderborn.de>
>>> ---
>>>   tests/tcg/tricore/Makefile | 30 +++++++++++++++++++++++
>>>   tests/tcg/tricore/link.ld  | 60 ++++++++++++++++++++++++++++++++++++++++++++++
>>>   2 files changed, 90 insertions(+)
>>>   create mode 100644 tests/tcg/tricore/Makefile
>>>   create mode 100644 tests/tcg/tricore/link.ld
>>>
>>> diff --git a/tests/tcg/tricore/Makefile b/tests/tcg/tricore/Makefile
>>> new file mode 100644
>>> index 0000000000..8c168d1062
>>> --- /dev/null
>>> +++ b/tests/tcg/tricore/Makefile
>>> @@ -0,0 +1,30 @@
>>> +AS := tricore-as
>>> +LD := tricore-ld
>> Where do these come from? Ideally we'd get these in a docker container
>> like the rest. It would actually be easier to use tricore-gcc if it
>> exists because at the moment my docker series only exposes a C compiler
>> to the make system.
> 
> I don't have access to gcc unfortunately. The only thing I can provide is the
> patched binutils (https://github.com/bkoppelmann/tricore-binutils).
> 
> Can you give me a pointer regarding your docker images?
> 
> Cheers,
> Bastian

Sorry Alex for taking this off list. I was at a new machine...

Cheers,
Bastian

  parent reply	other threads:[~2018-05-02  9:42 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-01 14:22 [Qemu-devel] [RFC PATCH 00/12] tests/tcg: Add TriCore tests Bastian Koppelmann
2018-05-01 14:22 ` [Qemu-devel] [RFC PATCH 01/12] hw/tricore: Add testdevice for tests in tests/tcg/ Bastian Koppelmann
2018-05-25 16:14   ` Alex Bennée
2018-05-01 14:22 ` [Qemu-devel] [RFC PATCH 02/12] tests/tcg/tricore: Add build infrastructure Bastian Koppelmann
2018-05-01 15:40   ` Alex Bennée
     [not found]     ` <f24f7977-cd8b-f502-e3f1-2ae6b0f422d8@mail.uni-paderborn.de>
2018-05-02  9:42       ` Bastian Koppelmann [this message]
2018-05-02 13:05         ` Alex Bennée
2018-05-02  0:41   ` Philippe Mathieu-Daudé
2018-05-02  9:26     ` Bastian Koppelmann
2018-05-02  9:50       ` Bastian Koppelmann
2018-05-01 14:22 ` [Qemu-devel] [RFC PATCH 03/12] tests/tcg/tricore: Add macros to easily create tests and first test 'abs' Bastian Koppelmann
2018-05-01 14:22 ` [Qemu-devel] [RFC PATCH 04/12] tests/tcg/tricore: Add bmerge test Bastian Koppelmann
2018-05-01 14:22 ` [Qemu-devel] [RFC PATCH 05/12] tests/tcg/tricore: Add clz test Bastian Koppelmann
2018-05-01 14:22 ` [Qemu-devel] [RFC PATCH 06/12] tests/tcg/tricore: Add dvstep test Bastian Koppelmann
2018-05-01 14:22 ` [Qemu-devel] [RFC PATCH 07/12] tests/tcg/tricore: Add fadd test Bastian Koppelmann
2018-05-01 14:22 ` [Qemu-devel] [RFC PATCH 08/12] tests/tcg/tricore: Add fmul test Bastian Koppelmann
2018-05-01 14:22 ` [Qemu-devel] [RFC PATCH 09/12] tests/tcg/tricore: Add ftoi test Bastian Koppelmann
2018-05-01 14:22 ` [Qemu-devel] [RFC PATCH 10/12] tests/tcg/tricore: Add madd test Bastian Koppelmann
2018-05-01 14:22 ` [Qemu-devel] [RFC PATCH 11/12] tests/tcg/tricore: Add msub test Bastian Koppelmann
2018-05-01 14:22 ` [Qemu-devel] [RFC PATCH 12/12] tests/tcg/tricore: Add muls test Bastian Koppelmann
2018-05-01 14:35 ` [Qemu-devel] [RFC PATCH 00/12] tests/tcg: Add TriCore tests no-reply

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=583cb654-2e10-14e2-faed-36c52a2f306a@mail.uni-paderborn.de \
    --to=kbastian@mail.uni-paderborn.de \
    --cc=alex.bennee@linaro.org \
    --cc=qemu-devel@nongnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.