From: Andreas Schwab <schwab@linux-m68k.org>
To: Matthew Wilcox <willy@infradead.org>
Cc: linux-m68k@lists.linux-m68k.org
Subject: Re: clear_bit_unlock_is_negative_byte
Date: Fri, 21 Jul 2023 14:52:56 +0200 [thread overview]
Message-ID: <87zg3pa0k7.fsf@igel.home> (raw)
In-Reply-To: <ZLpzNAIVVLH9JYZ1@casper.infradead.org> (Matthew Wilcox's message of "Fri, 21 Jul 2023 12:59:48 +0100")
On Jul 21 2023, Matthew Wilcox wrote:
> Do you happen to know if __GCC_ASM_FLAG_OUTPUTS__ is implemented for
> m68k so we can save the SMI instruction?
$ git grep __GCC_ASM_FLAG_OUTPUTS__ -- gcc/config
gcc/config/aarch64/aarch64-c.cc: builtin_define ("__GCC_ASM_FLAG_OUTPUTS__");
gcc/config/arm/arm-c.cc: def_or_undef_macro (pfile, "__GCC_ASM_FLAG_OUTPUTS__", !TARGET_THUMB1);
gcc/config/i386/i386-c.cc: cpp_define (parse_in, "__GCC_ASM_FLAG_OUTPUTS__");
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
next prev parent reply other threads:[~2023-07-21 12:53 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-20 19:27 clear_bit_unlock_is_negative_byte Matthew Wilcox
2023-07-20 22:37 ` clear_bit_unlock_is_negative_byte Michael Schmitz
2023-07-21 1:12 ` clear_bit_unlock_is_negative_byte Michael Schmitz
2023-07-21 1:32 ` clear_bit_unlock_is_negative_byte Matthew Wilcox
2023-07-21 1:43 ` clear_bit_unlock_is_negative_byte Michael Schmitz
2023-07-21 17:03 ` clear_bit_unlock_is_negative_byte Matthew Wilcox
2023-07-21 22:07 ` clear_bit_unlock_is_negative_byte Michael Schmitz
2023-07-22 6:24 ` clear_bit_unlock_is_negative_byte Andreas Schwab
2023-07-22 14:45 ` clear_bit_unlock_is_negative_byte Matthew Wilcox
2023-07-22 15:26 ` clear_bit_unlock_is_negative_byte Andreas Schwab
2023-07-22 15:38 ` clear_bit_unlock_is_negative_byte Matthew Wilcox
2023-07-21 6:34 ` clear_bit_unlock_is_negative_byte Andreas Schwab
2023-07-21 8:57 ` clear_bit_unlock_is_negative_byte Brad Boyer
2023-07-21 9:18 ` clear_bit_unlock_is_negative_byte Andreas Schwab
2023-07-21 11:59 ` clear_bit_unlock_is_negative_byte Matthew Wilcox
2023-07-21 12:52 ` Andreas Schwab [this message]
2023-07-21 20:29 ` clear_bit_unlock_is_negative_byte Brad Boyer
2023-07-22 3:42 ` clear_bit_unlock_is_negative_byte Matthew Wilcox
2023-07-22 23:49 ` clear_bit_unlock_is_negative_byte Brad Boyer
2023-07-23 1:08 ` clear_bit_unlock_is_negative_byte Michael Schmitz
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=87zg3pa0k7.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=willy@infradead.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.