This is adjusted patch only for OImode.
Bootstrapped and regtested on x86_64-pc-linux-gnu{-m32,}.
Ok for trunk?
gcc/ChangeLog:
PR target/104610
* config/i386/i386-expand.cc (ix86_expand_branch): Use ptest
for QImode when code is EQ or NE.
* config/i386/sse.md
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105504
--- Comment #4 from Hongtao.liu ---
Another possible solution is add a little bit dislike for "m" alternative(like
?m) to avoid potential spill.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105504
Hongtao.liu changed:
What|Removed |Added
CC||hjl.tools at gmail dot com
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105504
--- Comment #2 from Hongtao.liu ---
After set remove_partial_avx_dependency to true for register alternative, we
get
vxorps %xmm3, %xmm3, %xmm3
vmovsd .LC16(%rip), %xmm6
vmovsd .LC14(%rip), %xmm5
vcvtss2sd
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105504
--- Comment #1 from Hongtao.liu ---
Pass remove_partial_avx_dependency is before RA, which we have
(insn 128 127 129 22 (set (reg/v:DF 99 [ z ])
(float_extend:DF (reg/v:SF 117 [ x ]))) "test.c":43:10 163
{*extendsfdf2}
and attr
Hi,
On Tue, 2022-04-19 at 10:11 +0200, Richard Biener wrote:
> On Thu, 14 Apr 2022, Giuliano Belinassi wrote:
>
> > When -fpatchable-function-entry= is enabled, certain C++ codes
> > fails to
> > link because of generated references to discarded sections in
> > __patchable_function_entry
> -Original Message-
> From: Uros Bizjak
> Sent: Friday, May 6, 2022 4:59 PM
> To: Jiang, Haochen
> Cc: gcc-patches@gcc.gnu.org; Liu, Hongtao
> Subject: Re: [PATCH] [i386]Add combine splitter to transform
> pxor/pcmpeqb/pmovmskb/cmp 0x to ptest.
>
> On Fri, May 6, 2022 at 10:01
> -Original Message-
> From: Hongyu Wang
> Sent: Friday, May 6, 2022 4:50 PM
> To: Jiang, Haochen
> Cc: GCC Patches ; Liu, Hongtao
>
> Subject: Re: [PATCH] [i386]Add combine splitter to transform
> pxor/pcmpeqb/pmovmskb/cmp 0x to ptest.
>
> > +(define_split
> > + [(set (reg:CCZ
Hi Uros,
I understand that we always keep the old testcases there. It is always safe to
do that.
But I have another question, if we add something new in one of the existing
files in the future,
should we use __builtin_cpu_supports to keep the code clearer or stick to
cpuids?
I believe
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105511
Bug ID: 105511
Summary: Spurious warning: "expected 'template' keyword..."
when lt and gt compare over ternary
Product: gcc
Version: 11.2.0
Status: UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105331
--- Comment #7 from CVS Commits ---
The releases/gcc-11 branch has been updated by Jakub Jelinek
:
https://gcc.gnu.org/g:65c1c480b33ea36e9505ed444eed09a0cc1c9256
commit r11-9964-g65c1c480b33ea36e9505ed444eed09a0cc1c9256
Author: Jakub Jelinek
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105396
--- Comment #8 from CVS Commits ---
The releases/gcc-11 branch has been updated by Jakub Jelinek
:
https://gcc.gnu.org/g:79265f689bd831809d7d9a86f756d5dd3254d347
commit r11-9963-g79265f689bd831809d7d9a86f756d5dd3254d347
Author: Jakub Jelinek
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105333
--- Comment #6 from CVS Commits ---
The releases/gcc-11 branch has been updated by Jakub Jelinek
:
https://gcc.gnu.org/g:70d8bd6edae08bfc520dfb4b455b4592e3e2afe9
commit r11-9962-g70d8bd6edae08bfc520dfb4b455b4592e3e2afe9
Author: Jakub Jelinek
This patch to the Go fronend removes the is_lvalue_ field from
Array_index_expression. As of https://go.dev/cl/77510
(https://gcc.gnu.org/pipermail/gcc-patches/2017-November/487697.html)
it is never used. Bootstrapped and ran Go testsuite on
x86_64-pc-linux-gnu. Committed to mainline.
Ian
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105502
Jonathan Wakely changed:
What|Removed |Added
Summary|[9/10/11/12/13 Regression] |[9/10/11 Regression]
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105502
--- Comment #4 from CVS Commits ---
The releases/gcc-12 branch has been updated by Jonathan Wakely
:
https://gcc.gnu.org/g:03257e7ee31385a364b711898c8f1510fd638efe
commit r12-8354-g03257e7ee31385a364b711898c8f1510fd638efe
Author: Jonathan
Tested powerpc64le-linux, pushed to trunk. Backports to all branches
needed.
-- >8 --
This fixes a regression in std::normal_distribution deserialization that
caused the object to be left unchanged if the __state_avail value read
from the stream was false.
libstdc++-v3/ChangeLog:
PR
Tested powerpc64le-linux, pushed to trunk.
-- >8 --
libstdc++-v3/ChangeLog:
* include/bits/random.tcc (operator==): Only check
normal_distribution::_M_saved_available once.
* testsuite/26_numerics/random/normal_distribution/operators/equal.cc:
Check equality
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105502
--- Comment #3 from CVS Commits ---
The master branch has been updated by Jonathan Wakely :
https://gcc.gnu.org/g:909ef4e2727ddc50a32d6ad379a1f1ccc1043c6a
commit r13-163-g909ef4e2727ddc50a32d6ad379a1f1ccc1043c6a
Author: Jonathan Wakely
Date:
Snapshot gcc-11-20220506 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/11-20220506/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 11 git branch
with the following options: git://gcc.gnu.org/git/gcc.git branch
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102059
--- Comment #40 from CVS Commits ---
The releases/gcc-12 branch has been updated by Peter Bergner
:
https://gcc.gnu.org/g:e6b1ac334ac61f72536f3479f735ea3514f1309d
commit r12-8353-ge6b1ac334ac61f72536f3479f735ea3514f1309d
Author: Michael
On 5/5/22 16:00, Yonghong Song wrote:
On 5/4/22 10:03 AM, David Faust wrote:
On 5/3/22 15:32, Joseph Myers wrote:
On Mon, 2 May 2022, David Faust via Gcc-patches wrote:
Consider the following example:
#define __typetag1 __attribute__((btf_type_tag("tag1")))
#define
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105502
--- Comment #2 from Jonathan Wakely ---
Or:
--- a/libstdc++-v3/include/bits/random.tcc
+++ b/libstdc++-v3/include/bits/random.tcc
@@ -1961,7 +1961,7 @@ _GLIBCXX_BEGIN_NAMESPACE_VERSION
bool __saved_avail;
if (__is >> __mean >>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105501
anlauf at gcc dot gnu.org changed:
What|Removed |Added
CC||anlauf at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80196
--- Comment #17 from Jonathan Wakely ---
The problem for canadian crosses (comment 10 onwards) was PR 100017 and is
fixed now.
On Fri, 6 May 2022, Jason Merrill wrote:
> On 5/6/22 16:10, Patrick Palka wrote:
> > On Fri, 6 May 2022, Patrick Palka wrote:
> >
> > > On Fri, 6 May 2022, Jason Merrill wrote:
> > >
> > > > On 5/6/22 14:00, Patrick Palka wrote:
> > > > > On Fri, 6 May 2022, Patrick Palka wrote:
> > > > >
> >
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80196
--- Comment #16 from Jonathan Wakely ---
(In reply to Eddy L O Jansson from comment #15)
> For reasons that I'll skip, between the successful build of 12.0.1 and now I
> had added:
>
> export
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105473
--- Comment #5 from anlauf at gcc dot gnu.org ---
(In reply to Jerry DeLisle from comment #4)
> I see I no longer have change status on PRs. Evidently some of the address
> and login changes I have had to do in the process of changing my email
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105501
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Last reconfirmed||2022-05-06
Calling count.apply_scale with a 0 denominator causes an assert.
This change guards against that.
Tested on x86_64-pc-linux-gnu.
gcc/ChangeLog:
* tree-loop-vect-manip.cc (vect_do_peeling): Guard against applying
scale with 0 denominator.
---
gcc/tree-vect-loop-manip.cc | 9 +
1
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100111
--- Comment #12 from CVS Commits ---
The master branch has been updated by Jason Merrill :
https://gcc.gnu.org/g:967cdbe66296535fa496b88406a1125c8acaf6e2
commit r13-160-g967cdbe66296535fa496b88406a1125c8acaf6e2
Author: Jason Merrill
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105245
--- Comment #4 from CVS Commits ---
The master branch has been updated by Jason Merrill :
https://gcc.gnu.org/g:967cdbe66296535fa496b88406a1125c8acaf6e2
commit r13-160-g967cdbe66296535fa496b88406a1125c8acaf6e2
Author: Jason Merrill
Date:
While looking at PR105245 in stage 4, I wanted to reorganize the code a bit,
but it seemed prudent to defer that to stage 1.
Tested x86_64-pc-linux-gnu, applying to trunk.
PR c++/105245
PR c++/100111
gcc/cp/ChangeLog:
* constexpr.cc (cxx_eval_store_expression):
On 5/6/22 16:10, Patrick Palka wrote:
On Fri, 6 May 2022, Patrick Palka wrote:
On Fri, 6 May 2022, Jason Merrill wrote:
On 5/6/22 14:00, Patrick Palka wrote:
On Fri, 6 May 2022, Patrick Palka wrote:
On Fri, 6 May 2022, Jason Merrill wrote:
On 5/6/22 11:22, Patrick Palka wrote:
Here
On Fri, 6 May 2022, Patrick Palka wrote:
> On Fri, 6 May 2022, Jason Merrill wrote:
>
> > On 5/6/22 14:00, Patrick Palka wrote:
> > > On Fri, 6 May 2022, Patrick Palka wrote:
> > >
> > > > On Fri, 6 May 2022, Jason Merrill wrote:
> > > >
> > > > > On 5/6/22 11:22, Patrick Palka wrote:
> > > >
On Fri, 6 May 2022, Jason Merrill wrote:
> On 5/6/22 14:00, Patrick Palka wrote:
> > On Fri, 6 May 2022, Patrick Palka wrote:
> >
> > > On Fri, 6 May 2022, Jason Merrill wrote:
> > >
> > > > On 5/6/22 11:22, Patrick Palka wrote:
> > > > > Here ever since r10-7313-gb599bf9d6d1e18,
> > > > >
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102059
--- Comment #39 from CVS Commits ---
The releases/gcc-10 branch has been updated by Peter Bergner
:
https://gcc.gnu.org/g:aa33a2d866c0f3f2f9b3cb26f8ff2074bcd169b4
commit r10-10596-gaa33a2d866c0f3f2f9b3cb26f8ff2074bcd169b4
Author: Michael
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80196
Eddy L O Jansson changed:
What|Removed |Added
CC||eddy at klopper dot net
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105510
Bug ID: 105510
Summary: [12] error: initializer element is not constant
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component:
On May 6, 2022, Jonathan Wakely wrote:
> On Fri, 6 May 2022 at 17:17, Segher Boessenkool wrote:
>> > +#if defined __VSX__ || __LONG_WIDTH__ == 32
>> > _GLIBCXX_SIMD_PPC_INTRIN(signed long);
>> > _GLIBCXX_SIMD_PPC_INTRIN(unsigned long);
>> > +#endif
>>
>> Is __LONG_WIDTH__ the right macro to
On 5/6/22 14:00, Patrick Palka wrote:
On Fri, 6 May 2022, Patrick Palka wrote:
On Fri, 6 May 2022, Jason Merrill wrote:
On 5/6/22 11:22, Patrick Palka wrote:
Here ever since r10-7313-gb599bf9d6d1e18, reduced_constant_expression_p
in C++11/14 is rejecting the marked sub-aggregate initializer
This patch to the Go frontend rejects duplicate bool keys in a map
literal. This is hardly a common case, but we may as well get it
right. This is for https://go.dev/issue/35945 and
htps://go.dev/issue/28104. Bootstrapped and ran Go testsuite on
x86_64-pc-linux-gnu. Committed to mainline.
Ian
Hi!
On Fri, May 06, 2022 at 02:09:21PM +, Matthias Gehre via Gcc wrote:
> We would like to add support for division/modulo on large arbitrary precision
> integers to libgcc/compiler-rt
> as required by C23's _BitInt type [0].
>
> >From what I know, gcc doesn't yet support C23 _BitInt, but
UNSUBSCRIBE
On Fri, 6 May 2022, 14:57 Richard Biener via gcc-announce, <
gcc-annou...@gcc.gnu.org> wrote:
>
> The GCC developers are proud to announce another major GCC release, 12.1.
>
> This year we celebrated the 35th anniversary of the first GCC beta release
> and this month we will
On 2022-05-05 02:52, Alexandre Oliva wrote:
Regstrapped on x86_64-linux-gnu and ppc64le-linux-gnu, also tested
targeting ppc- and ppc64-vx7r2. Ok to install?
I am ok with the modified version of the patch. It looks reasonable for
me and I support its commit.
But I think I can not
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105472
H.J. Lu changed:
What|Removed |Added
Status|NEW |WAITING
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105472
--- Comment #3 from H.J. Lu ---
Created attachment 52935
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=52935=edit
A patch
On Fri, 6 May 2022, Patrick Palka wrote:
> On Fri, 6 May 2022, Jason Merrill wrote:
>
> > On 5/6/22 11:22, Patrick Palka wrote:
> > > Here ever since r10-7313-gb599bf9d6d1e18, reduced_constant_expression_p
> > > in C++11/14 is rejecting the marked sub-aggregate initializer (of type S)
> > >
> >
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105509
--- Comment #2 from Jonathan Wakely ---
(In reply to Thiago Macieira from comment #0)
> See also https://wg21.link/p1467, notably section 5.10 Literal suffixes
That isn't supported yet *at all*. And it's not in the C++ draft yet.
The current
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105509
--- Comment #1 from H.J. Lu ---
_Float16 was added for AVX512FP16 as a C++ extention. The fN suffixes were
added by
https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=c65699efcce48d68ef57ab3ce7fc5420fac5cbf9
which has
C++ note: no support for
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105472
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105472
--- Comment #1 from H.J. Lu ---
(In reply to Rainer Orth from comment #0)
>
> The usual way throughout the code base is to guard .note.GNU-stack with
> __ELF__ && __linux__ to avoid all this.
Isn't checking __linux__ sufficient?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105505
Jonathan Wakely changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
On Fri, 6 May 2022 at 17:17, Segher Boessenkool wrote:
> > +#if defined __VSX__ || __LONG_WIDTH__ == 32
> > _GLIBCXX_SIMD_PPC_INTRIN(signed long);
> > _GLIBCXX_SIMD_PPC_INTRIN(unsigned long);
> > +#endif
>
> Is __LONG_WIDTH__ the right macro to use here? Nothing else in
> libstdc++v3 uses it.
On 5/5/22 4:27 PM, Segher Boessenkool wrote:
> On Thu, May 05, 2022 at 02:59:07PM -0500, Peter Bergner wrote:
>> On 5/5/22 2:35 PM, Segher Boessenkool wrote:
>>> Just an unconditional
>>>
>>> callee_isa &= ~OPTION_MASK_P8_FUSION;
>>> explicit_isa &= ~OPTION_MASK_P8_FUSION;
>>>
>>> will do, no?
On Friday, May 6 2022, "Matthias Gehre" wrote to "lennox" saying:
> Jakub Jelinek wrote:
> > Rather than uint32_t, wouldn't using the word size (64-bit for lp64, 32-bit
> for ilp32) be better?
> Is there a portable way to specify this in C? (size_t, uintptr_t?) And is the
> word size
> clearly
> On May 6, 2022, at 10:58 AM, Uros Bizjak wrote:
>
> On Fri, May 6, 2022 at 4:29 PM Qing Zhao wrote:
>>
>> Hi,
>>
>> As Kee’s requested in this PR:
>> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101891
>>
>> =
>>
>> Currently -fzero-call-used-regs will use a pattern of:
>>
>> XOR
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102059
--- Comment #38 from CVS Commits ---
The master branch has been updated by Peter Bergner :
https://gcc.gnu.org/g:2fb654f77d5292864ef57040f7bc01d7a975f6d9
commit r13-157-g2fb654f77d5292864ef57040f7bc01d7a975f6d9
Author: Michael Meissner
Date:
On Fri, 6 May 2022, Jason Merrill wrote:
> On 5/6/22 11:22, Patrick Palka wrote:
> > Here ever since r10-7313-gb599bf9d6d1e18, reduced_constant_expression_p
> > in C++11/14 is rejecting the marked sub-aggregate initializer (of type S)
> >
> >W w = {.D.2445={.s={.D.2387={.m=0}, .b=0}}}
> >
Hi Chung-Lin,
thanks for the patch – and some comments from my side.
On 06.05.22 15:20, Chung-Lin Tang wrote:
For user defined allocator handles, this allows target regions to assign
memory space and traits to allocators, and automatically calls
omp_init/destroy_allocator() in the
On Mon, May 02, 2022 at 11:00:02PM -0300, Alexandre Oliva wrote:
> On May 2, 2022, Segher Boessenkool wrote:
> > Send full patches always please.
>
> I'll try to remember that. In case I fail, I hope you won't mind too
> much reminding me.
>
> (You'd also asked me not to send patches as
On Fri, May 06, 2022 at 11:56:30AM -0400, Jason Merrill via Gcc-patches wrote:
> On 5/6/22 11:22, Patrick Palka wrote:
> > Here ever since r10-7313-gb599bf9d6d1e18, reduced_constant_expression_p
> > in C++11/14 is rejecting the marked sub-aggregate initializer (of type S)
> >
> >W w =
On Fri, 6 May 2022, Matthias Gehre via Gcc wrote:
> > This proposed interface doesn't say anything about what aliasing is or
> > isn't permitted among the four arrays pointed to.
> Good catch. I would lean into saying that none of the four arrays must alias
> because allowing them to alias would
On Fri, May 6, 2022 at 4:29 PM Qing Zhao wrote:
>
> Hi,
>
> As Kee’s requested in this PR:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101891
>
> =
>
> Currently -fzero-call-used-regs will use a pattern of:
>
> XOR regA,regA
> MOV regA,regB
> MOV regA,regC
> ...
> RET
>
> However, this
> Note that each architecture also needs to specify its _BitInt ABI
> (including such things as whether the values of padding bits inside the
> size of the _BitInt type, or outside that size but within a register used
> for argument passing or return, have specified values or are arbitrary).
> HJ
On 5/6/22 11:22, Patrick Palka wrote:
Here ever since r10-7313-gb599bf9d6d1e18, reduced_constant_expression_p
in C++11/14 is rejecting the marked sub-aggregate initializer (of type S)
W w = {.D.2445={.s={.D.2387={.m=0}, .b=0}}}
^
ultimately because said initializer has
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105509
Bug ID: 105509
Summary: [compatibility] f16 suffix not supported in C++ mode -
unable to find numeric literal operator
‘operator""f16’
Product: gcc
Version:
This is a respin of:
https://gcc.gnu.org/pipermail/gcc-patches/2022-March/592307.html
that implements Richard's suggestion around the cgraph.cc change.
Otherwise the patch is as before.
Bootstrapped and regtested on aarch64-linux-gnu, OK for trunk?
Thanks,
Alex
--
I noticed that, while the
On Fri, May 06, 2022 at 02:09:21PM +, Matthias Gehre via Gcc wrote:
> /// \param quo The quotient represented by n words. Must be non-null.
> /// \param rem The remainder represented by n words. Must be non-null.
> /// \param a The dividend represented by n + 1 words. Must be non-null.
> ///
> -Original Message-
> From: Gcc-patches bounces+kyrylo.tkachov=arm@gcc.gnu.org> On Behalf Of Christophe
> Lyon via Gcc-patches
> Sent: Friday, May 6, 2022 4:19 PM
> To: gcc-patches@gcc.gnu.org
> Subject: [PATCH] aarch64: remove useless GPF_TF_F16 iterator
>
> This iterator is not
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105508
--- Comment #1 from 康桓瑋 ---
Reduced. In fact, I don't know if gcc is right here.
template
struct S {
int x = [b=1] { return b; }();
};
https://godbolt.org/z/fjqvePn5h
On Fri, 6 May 2022, Jakub Jelinek via Gcc wrote:
> And I really don't like the N + 1 stuff you're proposing, at least for
> _BigInts that would be represented as an array of those word etc. elements
> from least to most significant (or vice versa? That really needs to be
> specified too), if
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105508
Bug ID: 105508
Summary: declaration of 'const bool b' shadows template
parameter when defining concept using lambda
Product: gcc
Version: 12.0
Status: UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105507
Bug ID: 105507
Summary: Ada build fails for 32bit Windows
Product: gcc
Version: 12.1.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: ada
Here ever since r10-7313-gb599bf9d6d1e18, reduced_constant_expression_p
in C++11/14 is rejecting the marked sub-aggregate initializer (of type S)
W w = {.D.2445={.s={.D.2387={.m=0}, .b=0}}}
^
ultimately because said initializer has CONSTRUCTOR_NO_CLEARING set, and
so the
This iterator is not used anymore and is a leftover from previous
cleanup (r10-5890-gabbe1ed2735517).
2022-04-28 Christophe Lyon
gcc/
* config/aarch64/iterators.md (GPF_TF_F16): Delete.
---
gcc/config/aarch64/iterators.md | 3 ---
1 file changed, 3 deletions(-)
diff --git
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105506
Bug ID: 105506
Summary: Error building GCC 12.1.0 against MinGW-w64: fatal
error: cannot execute 'cc1': CreateProcess: No such
file or directory
Product: gcc
Hi H.J,
> On Mon, May 2, 2022 at 11:37 AM H.J. Lu wrote:
>>
>> On Fri, Apr 29, 2022 at 10:38 AM H.J. Lu wrote:
>> >
>> > Add .note.GNU-stack assembly source to avoid linker warning:
>> >
>> > ld: warning: /tmp/ccPZSZ7Z.o: missing .note.GNU-stack section implies
>> > executable stack
>> > ld:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105505
Bug ID: 105505
Summary: P1951R1 (Default Arguments for pair's Forwarding
Constructor) is unimplemented
Product: gcc
Version: 12.0
Status: UNCONFIRMED
On Fri, May 06, 2022 at 02:09:21PM +, Matthias Gehre via Gcc wrote:
> /// \param quo The quotient represented by n words. Must be non-null.
> /// \param rem The remainder represented by n words. Must be non-null.
> /// \param a The dividend represented by n + 1 words. Must be non-null.
> ///
On Thu, 5 May 2022, Martin Liška wrote:
> On 5/5/22 12:52, Alexander Monakov wrote:
> > Feels a bit weird to ask, but before entertaining such an API extension,
> > can we step back and understand the v3 variant of get_symbols? It is not
> > documented, and from what little I saw I did not get
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105433
H.J. Lu changed:
What|Removed |Added
Resolution|--- |FIXED
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105433
--- Comment #3 from CVS Commits ---
The releases/gcc-11 branch has been updated by H.J. Lu :
https://gcc.gnu.org/g:d38212762549d12b9c6428b1ff9fecbc05db2b99
commit r11-9961-gd38212762549d12b9c6428b1ff9fecbc05db2b99
Author: H.J. Lu
Date: Fri
On Mon, May 2, 2022 at 11:37 AM H.J. Lu wrote:
>
> On Fri, Apr 29, 2022 at 10:38 AM H.J. Lu wrote:
> >
> > Add .note.GNU-stack assembly source to avoid linker warning:
> >
> > ld: warning: /tmp/ccPZSZ7Z.o: missing .note.GNU-stack section implies
> > executable stack
> > ld: NOTE: This behaviour
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105433
--- Comment #2 from CVS Commits ---
The releases/gcc-12 branch has been updated by H.J. Lu :
https://gcc.gnu.org/g:e38194f5ad3074927aba811f7a71d19ea388e9bb
commit r12-8352-ge38194f5ad3074927aba811f7a71d19ea388e9bb
Author: H.J. Lu
Date: Fri
On Thu, May 5, 2022 at 2:02 PM H.J. Lu wrote:
>
> cherry-pick:
>
> b226894d475b [sanitizer] [sanitizer] Correct GetTls for x32
> ---
> libsanitizer/sanitizer_common/sanitizer_linux_libcdep.cpp | 4
> 1 file changed, 4 insertions(+)
>
> diff --git
On Fri, 6 May 2022, Matthias Gehre via Gcc wrote:
> We would like to add support for division/modulo on large arbitrary
> precision integers to libgcc/compiler-rt as required by C23's _BitInt
> type [0].
Note that each architecture also needs to specify its _BitInt ABI
(including such things
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105502
Jonathan Wakely changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |redi at gcc dot gnu.org
Hi,
As Kee’s requested in this PR:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101891
=
Currently -fzero-call-used-regs will use a pattern of:
XOR regA,regA
MOV regA,regB
MOV regA,regC
...
RET
However, this introduces both a register ordering dependency (e.g. the CPU
cannot clear regB
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102380
Bug 102380 depends on bug 99871, which changed state.
Bug 99871 Summary: #includes inside push visibility scope
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99871
What|Removed |Added
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99871
Jonathan Wakely changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
Hello!
We would like to add support for division/modulo on large arbitrary precision
integers to libgcc/compiler-rt
as required by C23's _BitInt type [0].
>From what I know, gcc doesn't yet support C23 _BitInt, but we would still
like to ensure that libgcc and compiler-rt can stay compatible in
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104731
--- Comment #5 from Jonathan Wakely ---
This should be fixed on trunk, but I'm unable to test on Solaris right now:
ld.so.1: g++: fatal: relocation error: file
/export/home/jwakely/gcc/12/bin/g++: symbol stpcpy: referenced symbol not found
On Solaris the dirent::d_name member is a single char, causing this test
to fail with warnings about buffer overflow. Change the test to use a
union with additional space for writing a string to the d_name member.
libstdc++-v3/ChangeLog:
PR libstdc++/104731
*
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104731
--- Comment #4 from CVS Commits ---
The master branch has been updated by Jonathan Wakely :
https://gcc.gnu.org/g:aa8bdfee1db818b9a56908ab0197ff02c54bf281
commit r13-154-gaa8bdfee1db818b9a56908ab0197ff02c54bf281
Author: Jonathan Wakely
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105491
Patrick Palka changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned
Tested powerpc64le-linux, pushed to trunk.
-- >8 --
This avoids polluting the global namespace with the "abi" namespace
alias.
libstdc++-v3/ChangeLog:
* include/std/stacktrace: Do not include .
(__cxa_demangle): Declare.
---
libstdc++-v3/include/std/stacktrace | 8 +++-
1
Tested powerpc64le-linux, pushed to trunk.
-- >8 --
libstdc++-v3/ChangeLog:
PR libstdc++/99871
* include/bits/specfun.h: Use visibility attribute on namespace,
instead of pragma push/pop.
* libsupc++/compare: Likewise.
* libsupc++/exception: Likewise.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99871
--- Comment #4 from CVS Commits ---
The master branch has been updated by Jonathan Wakely :
https://gcc.gnu.org/g:488d268728bf701ac76a1392eaed202c80be3843
commit r13-152-g488d268728bf701ac76a1392eaed202c80be3843
Author: Jonathan Wakely
Date:
I've pushed this to trunk now.
On Thu, 28 Apr 2022 at 18:02, Jonathan Wakely wrote:
>
> On Thu, 28 Apr 2022 at 17:45, Koning, Paul via Libstdc++
> wrote:
> >
> >
> >
> > > On Apr 28, 2022, at 8:37 AM, Jonathan Wakely via Gcc-patches
> > > wrote:
> > >
> > > I intend to commit this patch soon.
1 - 100 of 307 matches
Mail list logo
