From: Jakub Jelinek <jakub@redhat.com>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: Martin Sebor <msebor@gmail.com>,
Gcc Patch List <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] diagnose unsupported uses of hardware register variables (PR 88000)
Date: Wed, 14 Nov 2018 12:14:00 -0000 [thread overview]
Message-ID: <20181114121437.GT11625@tucnak> (raw)
In-Reply-To: <20181114121136.GY23873@gate.crashing.org>
On Wed, Nov 14, 2018 at 06:11:37AM -0600, Segher Boessenkool wrote:
> It doesn't "break" anything because it currently isn't guaranteed to work
> either. There is __builtin_frame_address(0) for this of course (well,
> almost the same semantics, and it is actually well-defined and actually
> works). Is there user code that tries to do this with a register var?
I've seen such code many times over the years, don't have time to perform
code searches for such kind of constructs now though.
Jakub
next prev parent reply other threads:[~2018-11-14 12:14 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-14 4:11 Martin Sebor
2018-11-14 9:39 ` Alexander Monakov
2018-11-15 22:34 ` Martin Sebor
2018-11-14 9:48 ` Jakub Jelinek
2018-11-14 11:35 ` Segher Boessenkool
2018-11-14 11:40 ` Jakub Jelinek
2018-11-14 11:50 ` Segher Boessenkool
2018-11-14 12:00 ` Jakub Jelinek
2018-11-14 12:11 ` Segher Boessenkool
2018-11-14 12:14 ` Jakub Jelinek [this message]
2018-11-15 18:31 ` Martin Sebor
2018-11-14 12:22 Segher Boessenkool
2018-11-14 12:27 ` Jakub Jelinek
2018-11-14 12:33 ` Alexander Monakov
2018-11-14 13:53 ` Segher Boessenkool
2018-11-14 15:50 ` Alexander Monakov
2018-11-14 17:47 ` Segher Boessenkool
2018-11-14 18:01 ` Alexander Monakov
2018-11-15 15:54 ` Michael Matz
2018-11-15 16:23 ` Alexander Monakov
2018-11-16 15:21 ` Michael Matz
2018-11-16 16:28 ` Alexander Monakov
2018-11-16 16:43 ` Michael Matz
2018-11-16 22:12 ` Segher Boessenkool
2018-11-19 12:59 ` Michael Matz
2018-11-19 17:18 ` Segher Boessenkool
2018-11-14 13:47 ` Segher Boessenkool
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=20181114121437.GT11625@tucnak \
--to=jakub@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=msebor@gmail.com \
--cc=segher@kernel.crashing.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).