public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: ASSI <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] Test: gcc-11.3.1+20230310-0.1
Date: Tue, 14 Mar 2023 18:44:21 +0100	[thread overview]
Message-ID: <87jzzj4496.fsf@Otto.invalid> (raw)
In-Reply-To: <362e1022-449a-e3d1-f0d4-08c12d7c86a3@cornell.edu> (Ken Brown via Cygwin's message of "Mon, 13 Mar 2023 17:00:46 -0400")

Ken Brown via Cygwin writes:
> On 3/11/2023 1:50 PM, Achim Gratz via Cygwin wrote:
>> The native Gcc compilers have been updated to the latest upstream
>> snapshot version of the gcc-11 branch:
>>   gcc-11.3.1+20230310
>
> I've given it a pretty good workout with builds of Emacs and TeX Live,
> and everything seems good so far.

Thank you for taking the time to test it.

>> This release includes libgccjit as a separate package for the native
>> toolchain.  Since Cygwin does not yet enable ASLR by default, any
>> nontrivial dynamic objects that are created in this way will likely need
>> to get rebased before they can be used.  It is unlikely that build
>> systems recognize the need for doing that at the moment.
>
> FYI, following a suggestion made by Corinna on IRC, I'm building all
> the Emacs libraries (.eln files as well as tree-sitter grammar libs)
> with ASLR enabled and no rebasing.  I have about 400 of these
> libraries on my system.  I've been doing this for about a month
> without any fork failures.

The real test is to see what happens when a collision does occur.  In
WinXP times the only reliable way out was a reboot when that happened…
which is why I gave up at the time.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Wavetables for the Waldorf Blofeld:
http://Synth.Stromeko.net/Downloads.html#BlofeldUserWavetables

      reply	other threads:[~2023-03-14 17:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-11 18:50 Achim Gratz
2023-03-13 21:00 ` Ken Brown
2023-03-14 17:44   ` ASSI [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=87jzzj4496.fsf@Otto.invalid \
    --to=stromeko@nexgo.de \
    --cc=cygwin@cygwin.com \
    /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).