From: Jeff Law <law@redhat.com>
To: coypu@sdf.org
Cc: gcc-patches@gcc.gnu.org, krister.walfridsson@gmail.com, rth@twiddle.net
Subject: Re: [PATCH, alpha] Move linux-specific specfile definitions to linux.h
Date: Sun, 19 Nov 2017 23:28:00 -0000 [thread overview]
Message-ID: <22977844-2693-dd6c-54ad-eee2315e4770@redhat.com> (raw)
In-Reply-To: <20171025012608.GA25388@SDF.ORG>
On 10/24/2017 07:26 PM, coypu@sdf.org wrote:
> On Fri, Oct 13, 2017 at 11:13:52AM -0600, Jeff Law wrote:
>> So we can't depend on patches that OpenBSD applies. What's important is
>> what is in the official GCC sources.
>>
>> I'd like to see some discussion about what these macros should look like
>> for the *bsd ports. Merely removing them from elf.h without providing
>> something for the *bsd ports seems wrong to me.
>
> Hi Jeff,
>
> OpenBSD has no crt1.o, crtn.o, and crtfastmath.o Linking to those
> would fail. As testimony: they are overriding it locally.
>
> And journalists may say, "OpenBSD has declined to comment on this patch".
But it does have other crt files such as crt0.o, crtend.o, crtbegin.o
that are supposed to be handled by the SPEC files.
Pulling these out of elf.h *may* still be sensible, but it really
doesn't seem to address the problem of what the proper definition should
be for OpenBSD.
jeff
prev parent reply other threads:[~2017-11-19 23:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-03 15:47 Maya Rashish
2017-10-13 17:14 ` Jeff Law
2017-10-25 2:24 ` coypu
2017-11-19 23:28 ` Jeff Law [this message]
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=22977844-2693-dd6c-54ad-eee2315e4770@redhat.com \
--to=law@redhat.com \
--cc=coypu@sdf.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=krister.walfridsson@gmail.com \
--cc=rth@twiddle.net \
/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).