Snapshot gcc-10-20211001 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/10-20211001/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 10 git branch
with the following options: git://gcc.gnu.org/git/gcc.git branch
On 10/1/21 11:44 AM, Florian Weimer wrote:
* Martin Sebor via Gcc:
I'd expect TYPE_NEEDS_CONSTRUCTING to be non-zero in the middle end
for any C++ type with a user-defined ctor, but in some of my testing
I see it's actually zero for std::string, at least in some instances
(but nonzero for other
I suppose I should answer my own question
Yes, the final compiler built has ubsan enabled.
Gary
PS. The faint hearted should note this is an overnight build. It would be nice
if this wasn't tied to building a bootstrap compiler.
From: Gary Oblock
Sent: Wed
* Martin Sebor via Gcc:
> I'd expect TYPE_NEEDS_CONSTRUCTING to be non-zero in the middle end
> for any C++ type with a user-defined ctor, but in some of my testing
> I see it's actually zero for std::string, at least in some instances
> (but nonzero for other types with ctors). Is there somethin
Hello.
Firstly I want to apologize for this long post, but in a way this post also
is meant for documenting the work that I have done hunting down this issue.
Secondly I must say that I do not have much insights on the GCC internals,
only the basic stuff. I know what a function prologue and epilog
I'd expect TYPE_NEEDS_CONSTRUCTING to be non-zero in the middle end
for any C++ type with a user-defined ctor, but in some of my testing
I see it's actually zero for std::string, at least in some instances
(but nonzero for other types with ctors). Is there something special
about std::string that
On Wed, 22 Sep 2021, Aldy Hernandez via Gcc wrote:
> Well, it turns out we're considerably better than reported.
>
> Andrew just found a one-line change in the path solver that improves
> our VRP threading goodness to 18.5% and our overall jump threading
> gains to 1.28%.
Would that make a great
On Wed, 29 Sep 2021, Maxim Kuvyrkov via Gcc wrote:
> Configurations that track master branches have 3-day intervals.
> Configurations that track release branches — 6 days. If a regression is
> detected it is narrowed down to component first — binutils, gcc or glibc
> — and then the commit rang
> On 29 Sep 2021, at 21:21, Andrew MacLeod wrote:
>
> On 9/29/21 7:59 AM, Maxim Kuvyrkov wrote:
>>
>>> Does it run like once a day/some-time-period, and if you note a
>>> regression, narrow it down?
>> Configurations that track master branches have 3-day intervals.
>> Configurations that tr
Status
==
The GCC development branch is open for general development (Stage 1),
but the two-month general bugfixing period (Stage 3) is ahead with
historical data telling us to expect it to start Nov 15th and last
through the Christmas holidays.
Take the quality data below with a big grain
10 matches
Mail list logo
