From: Daniel Cederman <cederman@gaisler.com>
To: Eric Botcazou <ebotcazou@libertysurf.fr>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] sparc: Char arrays are 64-bit aligned on SPARC
Date: Mon, 8 Jan 2024 12:42:35 +0100 [thread overview]
Message-ID: <fe97bc63-ceab-49fc-a70c-336648da92c7@gaisler.com> (raw)
In-Reply-To: <4887959.31r3eYUQgx@fomalhaut>
On 2024-01-08 10:20, Eric Botcazou wrote:
>> pr88077 fails on SPARC since char HeaderStr[1] in pr88077_1.c and
>> long HeaderStr in pr88077_0.c differs in alignment.
>>
>> warning: alignment 4 of normal symbol `HeaderStr' in c_lto_pr88077_0.o is
>> smaller than 8 used by the common definition in c_lto_pr88077_1.o
>
> I have never seen it though. Is that really a warning issued by GCC?
>
Hello Eric! Thank you for reviewing the patches!
No, this warning is not from GCC, it is from binutils ld. I forgot to
mention that in the message. I get a similar warning from older versions
of ld, so I do not think it is a new warning. It is also there with GCC 10.
For the OK:ed patches (with your changes), can I push them to
release/gcc-13 in addition to master?
/Daniel
next prev parent reply other threads:[~2024-01-08 11:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-05 7:19 Daniel Cederman
2024-01-05 7:19 ` [PATCH 1/2] sparc: Revert membar optimization that is not suitable for LEON5 Daniel Cederman
2024-01-08 9:22 ` Eric Botcazou
2024-01-05 7:19 ` [PATCH] sparc: Treat instructions with length 0 as empty Daniel Cederman
2024-01-08 9:26 ` Eric Botcazou
2024-01-05 7:19 ` [PATCH 2/2] sparc: Add errata workaround to membar patterns Daniel Cederman
2024-01-08 9:32 ` Eric Botcazou
2024-01-08 9:20 ` [PATCH] sparc: Char arrays are 64-bit aligned on SPARC Eric Botcazou
2024-01-08 11:42 ` Daniel Cederman [this message]
2024-01-09 8:45 ` Eric Botcazou
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=fe97bc63-ceab-49fc-a70c-336648da92c7@gaisler.com \
--to=cederman@gaisler.com \
--cc=ebotcazou@libertysurf.fr \
--cc=gcc-patches@gcc.gnu.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).