From: Mark Wielaard <mark@klomp.org>
To: Michael Eager <eager@eagercon.com>
Cc: appa.rao.nali@amd.com, binutils@sourceware.org,
ibai.erkiaga-elorza@amd.com, luca.ceresoli@bootlin.com,
mark.hatle@amd.com, nagaraju.mekala@amd.com, neal.frager@amd.com,
nickc@redhat.com, sadanand.mutyala@amd.com,
vidhumouli.hunsigida@amd.com
Subject: Re: [PATCH] microblaze: fix build error on 32-bit hosts
Date: Sun, 8 Oct 2023 01:14:07 +0200 [thread overview]
Message-ID: <20231007231407.GC728@gnu.wildebeest.org> (raw)
In-Reply-To: <ab1b696c-2712-05d3-6fe0-028f9db2641b@eagercon.com>
Hi,
On Sat, Oct 07, 2023 at 04:07:30PM -0700, Michael Eager wrote:
>
> Building with GCC-13.2.1 on Fedora 38 -- no error messages.
>
> >Which version of GCC are you using?
gcc (Debian 10.2.1-6) 10.2.1 20210110 on debian-i386.
But I don't think it depends on the gcc version. It depends on having
an 32bit host that is configured with --enable-targets=all.
Cheers,
Mark
next prev parent reply other threads:[~2023-10-07 23:14 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-05 12:51 [PATCH v2 1/1] opcodes: microblaze: Add new bit-field instructions Neal Frager
2023-10-06 19:17 ` Michael Eager
2023-10-07 19:23 ` Maciej W. Rozycki
2023-10-07 22:33 ` Michael Eager
2023-10-07 23:11 ` Michael Eager
2023-10-09 6:32 ` Frager, Neal
2023-10-09 13:32 ` Maciej W. Rozycki
2023-10-09 15:09 ` Michael Eager
2023-10-10 6:54 ` Frager, Neal
2023-10-10 16:16 ` Michael Eager
2023-10-10 17:54 ` Michael Eager
2023-10-09 10:53 ` Frager, Neal
2023-10-09 17:53 ` Michael Eager
2023-10-07 22:01 ` [PATCH] microblaze: fix build error on 32-bit hosts Mark Wielaard
2023-10-07 22:53 ` Michael Eager
2023-10-07 23:07 ` Michael Eager
2023-10-07 23:14 ` Mark Wielaard [this message]
2023-10-09 11:58 ` Frager, Neal
2023-10-09 12:37 ` Mark Wielaard
2023-10-09 12:42 ` Frager, Neal
2023-10-09 12:48 ` Mark Wielaard
2023-10-09 12:56 ` Frager, Neal
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=20231007231407.GC728@gnu.wildebeest.org \
--to=mark@klomp.org \
--cc=appa.rao.nali@amd.com \
--cc=binutils@sourceware.org \
--cc=eager@eagercon.com \
--cc=ibai.erkiaga-elorza@amd.com \
--cc=luca.ceresoli@bootlin.com \
--cc=mark.hatle@amd.com \
--cc=nagaraju.mekala@amd.com \
--cc=neal.frager@amd.com \
--cc=nickc@redhat.com \
--cc=sadanand.mutyala@amd.com \
--cc=vidhumouli.hunsigida@amd.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).