public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
To: Iain Buclaw <ibuclaw@gdcproject.org>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] libphobos: Allow building libphobos using Solaris/x86 assembler
Date: Tue, 05 Jan 2021 22:57:12 +0100	[thread overview]
Message-ID: <yddble3f3nr.fsf@CeBiTec.Uni-Bielefeld.DE> (raw)
In-Reply-To: <20210105214349.3401864-1-ibuclaw@gdcproject.org> (Iain Buclaw's message of "Tue, 5 Jan 2021 22:43:49 +0100")

Hi Iain,

> This patch removes the disabling of libphobos when the Solaris/x86
> assembler is being used.
>
> Since r11-6373, D symbols are now compressed using back references, this
> helped reduce the average symbol length by a factor of about 3, while
> the longest symbol shrank from 416133 to 1142 characters.  So the issues
> that were seen on Solaris/x86 should no longer be a problem.
>
> However, I have only used x86_64-apple-darwin10 for testing, as
> libphobos couldn't be built on that target for the same reason, except
> it was the system linker segfaulting due to long symbol names.
>
> It would be good to know if Solaris has also benefitted from the change.

great, thanks.  I'll give this a whirl once today's regular bootstraps
have finished.

	Rainer

-- 
-----------------------------------------------------------------------------
Rainer Orth, Center for Biotechnology, Bielefeld University

  reply	other threads:[~2021-01-05 21:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-05 21:43 Iain Buclaw
2021-01-05 21:57 ` Rainer Orth [this message]
2021-01-06 13:57   ` Rainer Orth
2021-01-07 16:11     ` Iain Buclaw
2021-01-07 16:17       ` Rainer Orth
2021-01-07 17:48         ` Iain Buclaw
2021-01-11 16:46           ` Iain Buclaw
2021-01-12 14:54             ` Rainer Orth

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=yddble3f3nr.fsf@CeBiTec.Uni-Bielefeld.DE \
    --to=ro@cebitec.uni-bielefeld.de \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=ibuclaw@gdcproject.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).