Hi Carlos,
On Tue, Oct 29, 2024 at 06:02:03PM -0400, Carlos O'Donell via Gcc wrote:
> Recent discussions on the glibc mailing list make it clear
> that we need to expand and discuss more about our "why" along with
> the "what" and "how" of these changes.
Zoe wrote a good summary of that discussio
On Wed, 30 Oct 2024, Carlos O'Donell via Gcc wrote:
> Have you broken down those project goals into actionable steps that
> could be taken?
>
> For example filing Sourceware Infrastructure bugs for each service that
> needs to be migrated into a VM and isolated (with a top level tracker
> for
Hi Carlos,
On Wed, 2024-10-30 at 08:32 -0400, Carlos O'Donell wrote:
> I can get down to specific requirements and possible solutions for them,
> including
> things like securing logins with 2FA etc. Which *could* be solved by
> Sourceware
> today possibly using Nitrokeys (open hardware and FOSS
On 2024-10-30 11:45, Mark Wielaard wrote:
Hi Carlos,
On Wed, 2024-10-30 at 08:32 -0400, Carlos O'Donell wrote:
I can get down to specific requirements and possible solutions for
them, including
things like securing logins with 2FA etc. Which *could* be solved by
Sourceware
today possibly usin
On 10/30/24 11:45 AM, Mark Wielaard wrote:
> Hi Carlos,
>
> On Wed, 2024-10-30 at 08:32 -0400, Carlos O'Donell wrote:
>> I can get down to specific requirements and possible solutions for them,
>> including
>> things like securing logins with 2FA etc. Which *could* be solved by
>> Sourceware
>>
On Wed, 30 Oct 2024, Mark Wielaard wrote:
> Yes, we did already discuss this. But it is too early for that. Richard
> setup a wiki page for the Forge Experiment that includes a list of
> various bugs/issues in Forgejo that we would like to see resolved
> before we can call the experiment an succes
On 10/30/24 6:39 AM, Mark Wielaard wrote:
> Hi Carlos,
>
> On Tue, Oct 29, 2024 at 06:02:03PM -0400, Carlos O'Donell via Gcc wrote:
>> Recent discussions on the glibc mailing list make it clear
>> that we need to expand and discuss more about our "why" along with
>> the "what" and "how" of these c
Hi,
I think gcc is relying on undefined behaviour with the vcompress instruction.
Unfortunately my test case isn't reproducing on mainline, but gcc looks to
use the fields between the last mask selected field and vl while setting
tail agnostic.
This thread explains how vcompress is different in t
After a very successful first participation last year, we're excited to
announce that GCC will again have a developer room at the upcoming
FOSDEM 2025, in Brussels, Belgium:
https://fosdem.org/2025/
This email is a Call for Presentations about GCC for the developer
room.
Important Dates:
1s
