All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nick Desaulniers <ndesaulniers@google.com>
To: marc.zyngier@arm.com
Cc: Sami Tolvanen <samitolvanen@google.com>,
	christoffer.dall@arm.com,
	Takahiro Akashi <takahiro.akashi@linaro.org>,
	linux-arm-kernel@lists.infradead.org,
	kvmarm@lists.cs.columbia.edu, LKML <linux-kernel@vger.kernel.org>,
	Andrey Konovalov <andreyknvl@google.com>
Subject: Re: [PATCH] arm64: kvm: use -fno-jump-tables with clang
Date: Fri, 18 May 2018 10:41:22 -0700	[thread overview]
Message-ID: <CAKwvOdnuKda7paw=GZS5JG-0pGn4-+cWr68m4R+Sd6-=48Uy9Q@mail.gmail.com> (raw)
In-Reply-To: <CAKwvOdm1kYedukCq=g74AvqJHp6KC03oNoouQy2nkvfo4idoEw@mail.gmail.com>

+ Andrey (who reported testing this patch in
https://github.com/ClangBuiltLinux/linux/issues/11)
On Fri, May 18, 2018 at 10:40 AM Nick Desaulniers <ndesaulniers@google.com>
wrote:

> On Fri, May 18, 2018 at 10:30 AM Marc Zyngier <marc.zyngier@arm.com>
wrote:
> > I'm going to ask the question I've asked before when this patch cropped
> > up (must be the 4th time now):

> > Is it guaranteed that this is the only case where LLVM/clang is going to
> > generate absolute addresses instead of using relative addressing?

> It seems like if there's requirements that only relative addressing be
> used, then the compiler should be told explicitly about this restriction,
> no?
> --
> Thanks,
> ~Nick Desaulniers



-- 
Thanks,
~Nick Desaulniers

WARNING: multiple messages have this Message-ID (diff)
From: ndesaulniers@google.com (Nick Desaulniers)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm64: kvm: use -fno-jump-tables with clang
Date: Fri, 18 May 2018 10:41:22 -0700	[thread overview]
Message-ID: <CAKwvOdnuKda7paw=GZS5JG-0pGn4-+cWr68m4R+Sd6-=48Uy9Q@mail.gmail.com> (raw)
In-Reply-To: <CAKwvOdm1kYedukCq=g74AvqJHp6KC03oNoouQy2nkvfo4idoEw@mail.gmail.com>

+ Andrey (who reported testing this patch in
https://github.com/ClangBuiltLinux/linux/issues/11)
On Fri, May 18, 2018 at 10:40 AM Nick Desaulniers <ndesaulniers@google.com>
wrote:

> On Fri, May 18, 2018 at 10:30 AM Marc Zyngier <marc.zyngier@arm.com>
wrote:
> > I'm going to ask the question I've asked before when this patch cropped
> > up (must be the 4th time now):

> > Is it guaranteed that this is the only case where LLVM/clang is going to
> > generate absolute addresses instead of using relative addressing?

> It seems like if there's requirements that only relative addressing be
> used, then the compiler should be told explicitly about this restriction,
> no?
> --
> Thanks,
> ~Nick Desaulniers



-- 
Thanks,
~Nick Desaulniers

  reply	other threads:[~2018-05-18 17:41 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-18 17:02 [PATCH] arm64: kvm: use -fno-jump-tables with clang Sami Tolvanen
2018-05-18 17:02 ` Sami Tolvanen
2018-05-18 17:30 ` Marc Zyngier
2018-05-18 17:30   ` Marc Zyngier
2018-05-18 17:40   ` Nick Desaulniers
2018-05-18 17:40     ` Nick Desaulniers
2018-05-18 17:41     ` Nick Desaulniers [this message]
2018-05-18 17:41       ` Nick Desaulniers
2018-05-18 17:45     ` Marc Zyngier
2018-05-18 17:45       ` Marc Zyngier
2018-05-18 17:56       ` Nick Desaulniers
2018-05-18 17:56         ` Nick Desaulniers
2018-05-18 18:13         ` Marc Zyngier
2018-05-18 18:13           ` Marc Zyngier
2018-05-18 18:31           ` Nick Desaulniers
2018-05-18 18:31             ` Nick Desaulniers
2018-05-19 10:44             ` Marc Zyngier
2018-05-19 10:44               ` Marc Zyngier
2018-05-22 17:58               ` Andrey Konovalov
2018-05-22 17:58                 ` Andrey Konovalov
2018-05-22 18:28                 ` Nick Desaulniers
2018-05-22 18:28                   ` Nick Desaulniers
2018-05-23 11:54                   ` Andrey Konovalov
2018-05-23 11:54                     ` Andrey Konovalov
2018-05-23 17:47                     ` Nick Desaulniers
2018-05-23 17:47                       ` Nick Desaulniers
2018-05-23 18:57                       ` Andrey Konovalov
2018-05-23 18:57                         ` Andrey Konovalov

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='CAKwvOdnuKda7paw=GZS5JG-0pGn4-+cWr68m4R+Sd6-=48Uy9Q@mail.gmail.com' \
    --to=ndesaulniers@google.com \
    --cc=andreyknvl@google.com \
    --cc=christoffer.dall@arm.com \
    --cc=kvmarm@lists.cs.columbia.edu \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marc.zyngier@arm.com \
    --cc=samitolvanen@google.com \
    --cc=takahiro.akashi@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.