From: Andrew Stubbs <ams@codesourcery.com>
To: Thomas Schwinge <thomas@codesourcery.com>,
Martin Sebor <msebor@gmail.com>
Cc: <gcc-patches@gcc.gnu.org>, Hafiz Abid Qadeer <abidh@codesourcery.com>
Subject: Re: [PATCH libatomic/arm] avoid warning on constant addresses (PR 101379)
Date: Sat, 17 Jul 2021 23:28:45 +0100 [thread overview]
Message-ID: <2e085663-b619-5240-6a40-961420341ebd@codesourcery.com> (raw)
In-Reply-To: <87pmvii29w.fsf@euler.schwinge.homeip.net>
On 16/07/2021 18:42, Thomas Schwinge wrote:
> Of course, we may simply re-work the libgomp/GCN code -- but don't we
> first need to answer the question whether the current code is actually
> "bad"? Aren't we going to get a lot of similar reports from
> kernel/embedded/other low-level software developers, once this is out in
> the wild? I mean:
GCN already uses address 4 for this value because address 0 caused
problems with null-pointer checks.
It really ought not be this hard. :-(
Andrew
next prev parent reply other threads:[~2021-07-17 22:29 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-09 23:11 Martin Sebor
2021-07-15 8:33 ` Christophe Lyon
2021-07-16 17:42 ` Thomas Schwinge
2021-07-16 21:11 ` Martin Sebor
2021-07-19 8:49 ` Thomas Schwinge
2021-07-17 22:28 ` Andrew Stubbs [this message]
2021-07-19 8:46 ` [gcn] Work-around libgomp 'error: array subscript 0 is outside array bounds of ‘__lds struct gomp_thread * __lds[0]’ [-Werror=array-bounds]' (was: [PATCH libatomic/arm] avoid warning on constant addresses (PR 101379)) Thomas Schwinge
2021-07-19 8:56 ` Jakub Jelinek
2021-07-19 11:10 ` Andrew Stubbs
2021-07-20 7:23 ` [gcn] Work-around libgomp 'error: array subscript 0 is outside array bounds of ‘__lds struct gomp_thread * __lds[0]’ [-Werror=array-bounds]' Thomas Schwinge
2021-07-20 8:40 ` '#pragma GCC diagnostic' (mis-)use in 'statement' of 'if' (was: [gcn] Work-around libgomp 'error: array subscript 0 is outside array bounds of ‘__lds struct gomp_thread * __lds[0]’ [-Werror=array-bounds]') Thomas Schwinge
2021-07-20 19:47 ` '#pragma GCC diagnostic' (mis-)use in 'statement' of 'if' Martin Sebor
2021-07-20 20:16 ` Jakub Jelinek
2021-07-21 16:41 ` [PATCH libatomic/arm] avoid warning on constant addresses (PR 101379) Kyrylo Tkachov
2021-07-21 16:54 ` Martin Sebor
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=2e085663-b619-5240-6a40-961420341ebd@codesourcery.com \
--to=ams@codesourcery.com \
--cc=abidh@codesourcery.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=msebor@gmail.com \
--cc=thomas@codesourcery.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).