From: Florian Weimer <fweimer@redhat.com>
To: Harald van Dijk via Gcc-help <gcc-help@gcc.gnu.org>
Cc: Segher Boessenkool <segher@kernel.crashing.org>,
Harald van Dijk <harald@gigawatt.nl>
Subject: Re: Inline assembly and value extensions
Date: Mon, 05 Oct 2020 15:29:18 +0200 [thread overview]
Message-ID: <87ft6sx0lt.fsf@oldenburg2.str.redhat.com> (raw)
In-Reply-To: <f1ef59f7-8295-2c27-eb69-42637a135772@gigawatt.nl> (Harald van Dijk via Gcc-help's message of "Mon, 5 Oct 2020 14:26:19 +0100")
* Harald van Dijk via Gcc-help:
> In the x32 ABI, pointers do not have a single mode. They are SImode,
> except when passed as parameters or returned, in which case they are
> DImode (see the ix86_promote_function_mode function I mentioned). This
> is really the source of the problems.
I think that GCC cannot optimize away unecessary sign and zero
extensions is also a contributing factor, no?
Thanks,
Florian
--
Red Hat GmbH, https://de.redhat.com/ , Registered seat: Grasbrunn,
Commercial register: Amtsgericht Muenchen, HRB 153243,
Managing Directors: Charles Cachera, Brian Klemm, Laurie Krebs, Michael O'Neill
next prev parent reply other threads:[~2020-10-05 13:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-22 15:30 Harald van Dijk
2020-10-03 20:42 ` Harald van Dijk
2020-10-05 12:53 ` Segher Boessenkool
2020-10-05 13:26 ` Harald van Dijk
2020-10-05 13:29 ` Florian Weimer [this message]
2020-10-05 13:39 ` Harald van Dijk
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=87ft6sx0lt.fsf@oldenburg2.str.redhat.com \
--to=fweimer@redhat.com \
--cc=gcc-help@gcc.gnu.org \
--cc=harald@gigawatt.nl \
--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).