Fwd: Undelivered Mail Returned to Sender

[Akihiko Odaki]

Hi postmaster@amsat.org,

Apparently your system is rejected by Gmail. Could you fix the problem?

Thanks,
Akihiko Odaki

---------- Forwarded message ---------
From: Mail Delivery System <MAILER-DAEMON@mail-01.amsat.org>
Date: Wed, Feb 16, 2022 at 11:29 AM
Subject: Undelivered Mail Returned to Sender
To: <akihiko.odaki@gmail.com>


This is the mail system at host mail-01.amsat.org.

I'm sorry to have to inform you that your message could not
be delivered to one or more recipients. It's attached below.

For further assistance, please send mail to postmaster.

If you do so, please include this problem report. You can
delete your own text from the attached returned message.

                   The mail system

<philippe.mathieu.daude@gmail.com> (expanded from <f4bug@amsat.org>): host
    gmail-smtp-in.l.google.com[64.233.177.26] said: 550-5.7.1 [172.105.152.211
    12] Our system has detected that this message is 550-5.7.1 likely
    unsolicited mail. To reduce the amount of spam sent to Gmail, 550-5.7.1
    this message has been blocked. Please visit 550-5.7.1
    https://support.google.com/mail/?p=UnsolicitedMessageError 550 5.7.1  for
    more information. m141si25626293ybm.519 - gsmtp (in reply to end of DATA
    command)



---------- Forwarded message ----------
From: Akihiko Odaki <akihiko.odaki@gmail.com>
To: "Philippe Mathieu-Daudé" <f4bug@amsat.org>
Cc: qemu Developers <qemu-devel@nongnu.org>, Roman Bolshakov
<r.bolshakov@yadro.com>, Christian Schoenebeck
<qemu_oss@crudebyte.com>
Bcc:
Date: Wed, 16 Feb 2022 11:28:46 +0900
Subject: Re: [RFC PATCH 0/4] buildsys: More fixes to use GCC on macOS
On Tue, Feb 15, 2022 at 10:25 PM Philippe Mathieu-Daudé <f4bug@amsat.org> wrote:
>
> On 15/2/22 14:06, Akihiko Odaki wrote:
> > On Tue, Feb 15, 2022 at 9:06 PM Philippe Mathieu-Daudé <f4bug@amsat.org> 
> > wrote:
> >>
> >> Few fixes to be able to use GCC extensions which are not
> >> available on Clang.
> >>
> >> Philippe Mathieu-Daudé (4):
> >>    osdep: Avoid using Clang-specific __builtin_available()
> >>    osdep: Un-inline qemu_thread_jit_execute/write
> >>    audio: Rename coreaudio extension to use Objective-C compiler
> >>    ui/cocoa: Ignore 'initializer overrides' warnings
> >>
> >>   audio/{coreaudio.c => coreaudio.m} |  0
> >>   audio/meson.build                  |  2 +-
> >>   include/qemu/osdep.h               | 21 ++-------------------
> >>   ui/cocoa.m                         |  5 +++++
> >>   util/osdep.c                       | 20 ++++++++++++++++++++
> >>   5 files changed, 28 insertions(+), 20 deletions(-)
> >>   rename audio/{coreaudio.c => coreaudio.m} (100%)
> >>
> >> --
> >> 2.34.1
> >>
> >
> > Compiler portability is always nice to have. Making QEMU on macOS
> > compatible with GCC is good, but I don't think that would justify
> > abandoning compatibility with Clang.
>
> I am certainly not abandoning compatibility with Clang. What gives
> you this impression?

I read the description as it says it allows to introduce GCC
extensions which breaks builds with Clang.