public inbox for
 help / color / mirror / Atom feed
From: Corinna Vinschen <>
Subject: Re: [PATCH 1/6] cdefs.h: remove intel_compiler support
Date: Mon, 11 Jul 2022 10:32:18 +0200	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Jul 11 09:15, Sebastian Huber wrote:
> From: Warner Losh <>
> The  age  of   the  intel  compiler  support  is  so   old  as  to  be
> uninteresting. No recent recports of  intel compiler support have been
> received.  Remove  all the  special  case  workarounds for  the  Intel
> compiler. Should there be interest in supporting the compiler, contact
> me and I'll work with people to make it happen, though I suspect these
> instances are more likely to be in the way than to be helpful.

What about the Intel compiler support in newlib?  Not that I have seen any
evidence that somebody is actually using one...

Other than that, the patchset looks good to me.


  reply	other threads:[~2022-07-11  8:32 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-11  7:15 [PATCH 0/6] Synchronize <sys/cdefs.h> with FreeBSD Sebastian Huber
2022-07-11  7:15 ` [PATCH 1/6] cdefs.h: remove intel_compiler support Sebastian Huber
2022-07-11  8:32   ` Corinna Vinschen [this message]
2022-07-11  9:10     ` Sebastian Huber
2022-07-11  9:43       ` Corinna Vinschen
2022-07-11  7:15 ` [PATCH 2/6] Expose clang's alignment builtins and use them for roundup2/rounddown2 Sebastian Huber
2022-07-11  7:15 ` [PATCH 3/6] cdefs.h: Remove __GNUCLIKE___OFFSETOF, it's unused Sebastian Huber
2022-07-11  7:15 ` [PATCH 4/6] cdefs: Make __nosanitizeaddress work for KASAN as well Sebastian Huber
2022-07-11  7:15 ` [PATCH 5/6] cdefs: Add a default definition for __nosanitizememory Sebastian Huber
2022-07-11  7:15 ` [PATCH 6/6] cdefs.h: Remove redundant #ifdefs Sebastian Huber

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).