public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Paul Iannetta <piannetta@kalrayinc.com>
To: Alan Modra <amodra@gmail.com>
Cc: Luis Machado <luis.machado@arm.com>,
	Nick Clifton <nickc@redhat.com>,
	binutils@sourceware.org
Subject: Re: [PATCH v3] kvx: New port.
Date: Fri, 18 Aug 2023 09:13:24 +0200	[thread overview]
Message-ID: <20230818071323.66zycx7dlgfx3oso@ws2202.lin.mbt.kalray.eu> (raw)
In-Reply-To: <ZN6rLt+kpFpz2ObC@squeak.grove.modra.org>

On Fri, Aug 18, 2023 at 08:50:14AM +0930, Alan Modra wrote:
> On Thu, Aug 17, 2023 at 05:09:53PM +0200, Paul Iannetta via Binutils wrote:
> > On Thu, Aug 17, 2023 at 10:45:09AM +0100, Luis Machado wrote:
> > > 
> > > The builders have caught a few hiccups related to printf modifiers for 32-bit architectures.
> 
> > I was not able to fully reproduce but the attached patch should fix
> > the build errors.  However, we did not do any validation on 32 bits
> > hosts, so I think that even with this patch it will not be enough to
> > pass `make check'.
> 

I've tested it against a 32-bit host in a virtual machine and I
think it is enough to pass the build and the validation phase since
the `make check' does not seem to actually validate all targets but the
host so it should be fine.  I still need to improve the validation
when the kvx targets are validated on 32 bits hosts but I can do that
in a second time.

What is the process to get the changes merged?

> On x86_64-linux, I check a 32-bit host binutils compile using
> CC="gcc -m32" CXX="g++ -m32" \
> CFLAGS="-g -O2" CXXFLAGS="-g -O2" \
> ~/src/binutils-gdb/configure --build=i686-linux --enable-targets=all \
> --enable-gold --enable-threads --disable-gdb --disable-gdbserver \
> --disable-sim --disable-readline --disable-libdecnumber \
> --disable-libbacktrace --disable-gprofng --disable-nls
> 
> Specifying --build may not be necessary nowadays, this is from a very
> old recipe.

I'll try that thanks, it will be faster than using a virtual machine.

> >  I'll work on it so that everything pass by the end
> > of the week, so you may want to wait until I have also fixed the
> > validation before applying the patch.
> > 
> > Paul
> > 
> > 
> 
> > @@ -31,8 +31,8 @@ static reloc_howto_type elf_kvx_howto_table[] =
> >  	 bfd_elf_generic_reloc,		/* special_function */
> >  	 "R_KVX_NONE",			/* name */
> >  	 false,				/* partial_inplace */
> > -	 0,				/* src_mask */
> > -	 0,				/* dst_mask */
> > +	 (bfd_vma) 0,			/* src_mask */
> > +	 (bfd_vma) 0,			/* dst_mask */
> >  	 false),			/* pcrel_offset */
> >    HOWTO (R_KVX_16,			/* type */
> >  	 0,				/* rightshift */
> 
> Please don't add unnecessary casts like the above.
> 

This is a generated file, that is why the casts are everywhere. I'll
get rid of them when unnecessary.

Thanks
Paul





  reply	other threads:[~2023-08-18  7:13 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-21  7:49 [PATCH 0/7] " Paul Iannetta
2023-07-21  7:49 ` [PATCH 1/7] kvx: Add bf files Paul Iannetta
2023-07-21  7:49 ` [PATCH 2/7] kvx: Add binutils files Paul Iannetta
2023-07-21  7:49 ` [PATCH 3/7] kvx: Add gas file Paul Iannetta
2023-07-21  7:49 ` [PATCH 4/7] kvx: Add ld files Paul Iannetta
2023-07-21  7:49 ` [PATCH 5/7] kvx: Add include files Paul Iannetta
2023-07-21  7:49 ` [PATCH 6/7] kvx: Add opcodes file Paul Iannetta
2023-07-21  7:49 ` [PATCH 7/7] kvx: Add toplevel files Paul Iannetta
2023-07-21  8:29 ` [PATCH 0/7] kvx: New port Nick Clifton
     [not found]   ` <20230721090932.pspnpq2q2wjnshrh@ws2202.lin.mbt.kalray.eu>
     [not found]     ` <2050791e-38ee-5719-037f-c03c456f3e3d@redhat.com>
2023-07-21 16:47       ` Paul Iannetta
2023-07-21 17:00       ` Paul Iannetta
2023-07-21  8:57 ` YunQiang Su
2023-07-21 16:51   ` Paul Iannetta
2023-07-24  9:04 ` Nick Clifton
2023-07-24  9:38   ` Paul Iannetta
2023-07-24  9:28 ` Nick Clifton
2023-07-24 12:33   ` Paul Iannetta
2023-07-24 14:30     ` Paul Iannetta
2023-07-25 14:13     ` Nick Clifton
2023-07-26  7:36       ` Paul Iannetta
2023-07-26 13:32         ` Michael Matz
2023-07-26 21:46           ` Paul Iannetta
2023-07-26 21:24         ` [PATCH v2] " Paul Iannetta
2023-07-31 14:52           ` Nick Clifton
2023-08-02 14:38             ` [PATCH v3] " Paul Iannetta
2023-08-16 13:24               ` Nick Clifton
2023-08-17  9:45                 ` Luis Machado
2023-08-17 15:09                   ` Paul Iannetta
2023-08-17 16:28                     ` Luis Machado
2023-08-17 23:20                     ` Alan Modra
2023-08-18  7:13                       ` Paul Iannetta [this message]
2023-08-17 12:46                 ` Paul Iannetta
2023-07-24  9:53 ` [PATCH 0/7] " Nick Clifton
2023-07-24 12:27   ` Paul Iannetta

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=20230818071323.66zycx7dlgfx3oso@ws2202.lin.mbt.kalray.eu \
    --to=piannetta@kalrayinc.com \
    --cc=amodra@gmail.com \
    --cc=binutils@sourceware.org \
    --cc=luis.machado@arm.com \
    --cc=nickc@redhat.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).