From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Will Deacon <will.deacon@arm.com>
Cc: linux-arm-kernel@lists.infradead.org,
LKML <linux-kernel@vger.kernel.org>,
Mark Rutland <mark.rutland@arm.com>
Subject: Re: [PATCH] arm64: support __int128 on gcc 5+
Date: Tue, 31 Oct 2017 13:18:41 +0100 [thread overview]
Message-ID: <CAHmME9pey+8YcDg9+vkoVGU0qBkc6dqY7RXFYFr=RzcTb7qb+Q@mail.gmail.com> (raw)
In-Reply-To: <20171031121701.GI5584@arm.com>
On Tue, Oct 31, 2017 at 1:17 PM, Will Deacon <will.deacon@arm.com> wrote:
>
> Sure, I'll wait for your patch that matches the relevant compiler versions.
That's the patch in this thread:
http://lists.infradead.org/pipermail/linux-arm-kernel/2017-October/539943.html
As mentioned in there, gcc does the right thing for 5 and up:
https://gcc.gnu.org/git/?p=gcc.git;a=commitdiff;h=d1ae7bb994f49316f6f63e6173f2931e837a351d
next prev parent reply other threads:[~2017-10-31 12:18 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-31 10:17 CONFIG_ARCH_SUPPORTS_INT128 for AArch64 Jason A. Donenfeld
2017-10-31 10:43 ` Mark Rutland
2017-10-31 11:17 ` Jason A. Donenfeld
2017-10-31 11:43 ` [PATCH] arm64: support __int128 on gcc 5+ Jason A. Donenfeld
2017-10-31 11:51 ` Will Deacon
2017-10-31 11:57 ` Jason A. Donenfeld
2017-10-31 12:17 ` Will Deacon
2017-10-31 12:18 ` Jason A. Donenfeld [this message]
2017-11-02 13:47 ` Will Deacon
2017-11-02 17:43 ` [PATCH v2] " Jason A. Donenfeld
2017-11-03 13:42 ` Will Deacon
2017-11-03 14:02 ` Ard Biesheuvel
2017-11-03 14:14 ` Jason A. Donenfeld
2017-11-03 14:18 ` [PATCH v3] " Jason A. Donenfeld
2017-11-06 9:31 ` [PATCH v4] " Jason A. Donenfeld
2017-11-06 15:59 ` Catalin Marinas
2017-11-06 16:14 ` Catalin Marinas
[not found] ` <CAHmME9p+ef-+fmdiO15LU7X3Sr-CDyngpPwKZN2FqOQmZNjLtg@mail.gmail.com>
2017-11-06 16:55 ` Ard Biesheuvel
2017-11-06 23:58 ` [PATCH v5] " Jason A. Donenfeld
2017-11-07 0:01 ` [PATCH v4] " Jason A. Donenfeld
2017-11-07 2:13 ` Will Deacon
2017-11-07 2:16 ` Jason A. Donenfeld
2017-11-02 20:24 ` [PATCH] " Jason A. Donenfeld
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='CAHmME9pey+8YcDg9+vkoVGU0qBkc6dqY7RXFYFr=RzcTb7qb+Q@mail.gmail.com' \
--to=jason@zx2c4.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=will.deacon@arm.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 NNTP newsgroup(s).