public inbox for newlib@sourceware.org
 help / color / mirror / Atom feed
From: Corinna Vinschen <vinschen@redhat.com>
To: newlib@sourceware.org
Subject: Re: [PATCH] libc: Replace i386/sys/fenv.h symlink with an #include shim
Date: Tue, 23 Mar 2021 15:38:57 +0100	[thread overview]
Message-ID: <YFn9gfl5l+dvHzp4@calimero.vinschen.de> (raw)
In-Reply-To: <CAH2Hv8LfW8fJX+rhNmdgTECs4Buu4kiA0oeu1o_KSk=eVhbwqA@mail.gmail.com>

On Mar 13 19:11, David Macek via Newlib wrote:
> > > More to the point, how big of an issue would be to duplicate the file?
> >
> > I'm not hot on duplicating an identical file, it just raises maintenance
> > cost.  I'm currently looking into a solution to share the file without
> > duplicating it.
> 
> Something like a Makefile rule?

A bit more complicated in fact.  I added a new topic branch called
topic/shared_arch_headers to the upstream repo, containing a single
patch

  a8cd2849ed0c Add build mechanism to share common header files between
               machines

This patch introduces a new way to share header files between
architectures, not share by other architectures.

I tried to change this in a generic way.  The fenv stuff in this patch
is basically just the first user of this new mechanism.

As a side-effect, this also allows to remove Cygwin's own fenv code
finally, which was already pretty much the same as newlib's x86 code
anyway.  The major exception was the call to _feinitialise in Cygwin DLL
startup.  Given that the newlib fenv code is auto-initializing, this can
go away.  Cygwin just has to keep the _feinitialise entry point for
backward compatibility for apps built in a certain time frame.

David, Joel, anybody else interested in this stuff, please inspect
this patch on the topic/shared_arch_headers branch thorougly.  I will
not push this quickly, since we're in the process of releasing Cygwin
3.2.0.  I don't want to destabilise the release without need :)


Thanks,
Corinna


  parent reply	other threads:[~2021-03-23 14:39 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-07 15:03 David Macek
2021-03-08  9:59 ` Corinna Vinschen
2021-03-09 19:11   ` David Macek
2021-03-10  9:09     ` Corinna Vinschen
2021-03-11  7:13       ` David Macek
2021-03-11 14:11         ` Corinna Vinschen
2021-03-13 18:11           ` David Macek
2021-03-13 20:05             ` Joel Sherrill
2021-03-23 14:38             ` Corinna Vinschen [this message]
2021-03-24 10:15               ` Corinna Vinschen
2021-04-05  7:37                 ` David Macek
2021-04-06  9:57                   ` Corinna Vinschen
2021-04-07  7:28                     ` David Macek
2021-04-07  9:28                       ` Corinna Vinschen
2021-04-07 16:16                         ` David Macek
2021-04-13 11:00                           ` Corinna Vinschen

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=YFn9gfl5l+dvHzp4@calimero.vinschen.de \
    --to=vinschen@redhat.com \
    --cc=newlib@sourceware.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 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).