From: Nick Desaulniers <ndesaulniers@google.com>
To: Dmitry Vyukov <dvyukov@google.com>
Cc: Matthias Kaehlcke <mka@chromium.org>,
lukas.bulwahn@gmail.com, Greg Hackmann <ghackmann@google.com>,
Luis Lozano <llozano@google.com>,
Michael Davidson <md@google.com>,
Sami Tolvanen <samitolvanen@google.com>,
Paul Lawrence <paullawrence@google.com>,
Ingo Molnar <mingo@kernel.org>,
linux-mm@kvack.org, kasan-dev <kasan-dev@googlegroups.com>,
llvmlinux@lists.linuxfoundation.org, sil2review@lists.osadl.org,
manojgupta@chromium.org, Stephen Hines <srhines@google.com>
Subject: Re: clang fails on linux-next since commit 8bf705d13039
Date: Wed, 21 Mar 2018 17:07:38 +0000 [thread overview]
Message-ID: <CAKwvOd=S=ZqtfWM9RqYN9d_tUeHqhPFyEJoz4jBgXwYBvYJ3DA@mail.gmail.com> (raw)
In-Reply-To: <CACT4Y+ZsmWyvfcpCtxEUH3YJDDNFUAO=0kyCmJAfv=NXeVGRkA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 293 bytes --]
On Mon, Mar 19, 2018 at 11:16 AM Dmitry Vyukov <dvyukov@google.com> wrote:
> This looks like something that will hit us again and again if we don't
> fix this in clang.
>
I agree. I'll bring it up with some our coworkers who hack on the
integrated assembler.
--
Thanks,
~Nick Desaulniers
[-- Attachment #2: Type: text/html, Size: 1410 bytes --]
next prev parent reply other threads:[~2018-03-21 17:07 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-17 11:13 Lukas Bulwahn
2018-03-19 6:43 ` Dmitry Vyukov
2018-03-19 7:15 ` Lukas Bulwahn
2018-03-19 17:24 ` Nick Desaulniers
2018-03-19 17:29 ` Matthias Kaehlcke
2018-03-19 17:39 ` Dmitry Vyukov
2018-03-19 17:54 ` Matthias Kaehlcke
2018-03-19 18:15 ` Dmitry Vyukov
2018-03-21 17:07 ` Nick Desaulniers [this message]
[not found] ` <99fbbbe3-df05-446b-9ce0-55787ea038f3@googlegroups.com>
2018-05-06 10:44 ` Dmitry Vyukov
2018-05-06 10:48 ` Sedat Dilek
2018-05-07 7:34 ` Dmitry Vyukov
2018-05-28 16:05 ` [llvmlinux] " Sedat Dilek
2018-05-29 6:49 ` Jan Beulich
2018-06-01 13:14 ` Sedat Dilek
2018-07-29 18:12 ` Sedat Dilek
2018-07-30 8:21 ` Mark Rutland
2018-07-30 9:29 ` Sedat Dilek
2018-06-09 15:17 ` Sedat Dilek
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='CAKwvOd=S=ZqtfWM9RqYN9d_tUeHqhPFyEJoz4jBgXwYBvYJ3DA@mail.gmail.com' \
--to=ndesaulniers@google.com \
--cc=dvyukov@google.com \
--cc=ghackmann@google.com \
--cc=kasan-dev@googlegroups.com \
--cc=linux-mm@kvack.org \
--cc=llozano@google.com \
--cc=llvmlinux@lists.linuxfoundation.org \
--cc=lukas.bulwahn@gmail.com \
--cc=manojgupta@chromium.org \
--cc=md@google.com \
--cc=mingo@kernel.org \
--cc=mka@chromium.org \
--cc=paullawrence@google.com \
--cc=samitolvanen@google.com \
--cc=sil2review@lists.osadl.org \
--cc=srhines@google.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