From: Petr Vorel <pvorel@suse.cz>
To: Edward Liaw <edliaw@google.com>
Cc: kernel-team <kernel-team@android.com>, LTP List <ltp@lists.linux.it>
Subject: Re: [LTP] [PATCH v1] syscalls/signal06: add volatile to loop variable
Date: Fri, 19 Aug 2022 10:12:32 +0200 [thread overview]
Message-ID: <Yv9F8MnPGyLLE0Zm@pevik> (raw)
In-Reply-To: <CAG4es9WmHd52fmjdt7RBkSXEtnGuC2jkBO6UdCTbaHOq8CDgVw@mail.gmail.com>
> > On Wed, Aug 17, 2022, 2:12 AM Petr Vorel <pvorel@suse.cz> wrote:
> >> Hi Edward,
> >> Would you mind we delay merging after you fill the bug in llvm, so that
> >> we can
> >> add it to git commit message?
> Here's the link to the bug on llvm:
> https://github.com/llvm/llvm-project/issues/57234
Thanks! The bug was closed as 'adding "cx" worked'. Reading topperc's comment it
looks like there no other way to fix the issue on clang than workaround with
volatile. Does it mean that it's a syscall problem and clang can do nothing
about it?
Kind regards,
Petr
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2022-08-19 8:12 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-12 17:39 [LTP] [PATCH v1] syscalls/signal06: add volatile to loop variable Edward Liaw via ltp
2022-07-13 12:48 ` Petr Vorel
2022-07-19 10:20 ` Cyril Hrubis
2022-07-27 21:37 ` Edward Liaw via ltp
2022-08-11 15:24 ` Edward Liaw via ltp
2022-08-11 15:33 ` Cyril Hrubis
2022-08-16 12:43 ` Petr Vorel
2022-08-16 23:00 ` Edward Liaw via ltp
2022-08-17 9:12 ` Petr Vorel
2022-08-17 15:04 ` Edward Liaw via ltp
2022-08-18 21:18 ` Edward Liaw via ltp
2022-08-19 8:12 ` Petr Vorel [this message]
2022-08-19 8:41 ` Cyril Hrubis
2022-08-19 9:02 ` Cyril Hrubis
2022-08-19 9:14 ` Joerg Vehlow
2022-08-19 9:21 ` Cyril Hrubis
2022-08-19 10:40 ` Petr Vorel
2022-08-19 18:13 ` Edward Liaw via ltp
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=Yv9F8MnPGyLLE0Zm@pevik \
--to=pvorel@suse.cz \
--cc=edliaw@google.com \
--cc=kernel-team@android.com \
--cc=ltp@lists.linux.it \
/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.