https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107931
--- Comment #19 from rguenther at suse dot de ---
On Tue, 21 Feb 2023, ishikawa at yk dot rim.or.jp wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107931
>
> --- Comment #18 from ishikawa,chiaki ---
> I reported the issue to the follow
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108851
--- Comment #1 from Andrew Pinski ---
I doubt GCC has control over this. I suspect the issue is in the binutils side
...
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107931
--- Comment #18 from ishikawa,chiaki ---
I reported the issue to the following github for a very fast hashing function
library.
https://github.com/Cyan4973/xxHash/issues/800
>From the discussion there, I figured -Og does not define __NO_INLINE_
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108868
--- Comment #5 from Richard Biener ---
(In reply to Jakub Jelinek from comment #4)
> I think the reason why it doesn't work is clear, call_can_make_abnormal_goto
> on the vfork call is false, because it is leaf (and that is how glibc
> declares
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108846
--- Comment #7 from Andrew Pinski ---
I suspect std::move has the same issue too. The ability to use memmove with
trivial copyable subobjects ...
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108846
--- Comment #6 from Jiang An ---
> For example, assuming both sizeof(B) and sizeof(D) are 8, which means the last
> 2 bytes of B are padding (true for common implementations on Itanium ABI):
Oh, I forgot the strange design caused by CWG43 - thi
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108860
Jonathan Wakely changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Ever confirmed|0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98449
--- Comment #6 from Jonathan Wakely ---
(In reply to Vinícius dos Santos Oliveira from comment #3)
> LLVM's libcxx already applied this 1-line patchset:
> https://github.com/llvm/llvm-project/commit/
> 64fc3cd55d586498dd21c5b3cfaa755793913772
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108848
Patrick Palka changed:
What|Removed |Added
CC||ppalka at gcc dot gnu.org
Su
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108861
--- Comment #4 from Jonathan Wakely ---
(In reply to Vinícius dos Santos Oliveira from comment #2)
> Nobody is going to fix 98449. The ONE-line patchset fixing the issue was
> there for YEARS. Why does it take so many years to review ONE line? I
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108804
--- Comment #3 from Hongtao.liu ---
I think the point here is: although it's unit64_t -> float, but the range of x
and y can be represent as int32(k & 0x007F) | 0x3F80), so we can use
int32 -> float instructions which are supported by t
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108636
--- Comment #5 from CVS Commits ---
The releases/gcc-12 branch has been updated by Jonathan Wakely
:
https://gcc.gnu.org/g:0a2597477e482df4d67db6696431286df1ff4428
commit r12-9193-g0a2597477e482df4d67db6696431286df1ff4428
Author: Jonathan Wake
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108861
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98449
--- Comment #5 from Andrew Pinski ---
*** Bug 108861 has been marked as a duplicate of this bug. ***
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98449
Andrew Pinski changed:
What|Removed |Added
Status|RESOLVED|SUSPENDED
Resolution|FIXED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108868
--- Comment #4 from Jakub Jelinek ---
I think the reason why it doesn't work is clear, call_can_make_abnormal_goto on
the vfork call is false, because it is leaf (and that is how glibc declares
vfork BTW) and ctrl_altering flag is initialized by
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108861
--- Comment #2 from Vinícius dos Santos Oliveira ---
> Isn't this just Bug 98449? Why did you close that as FIXED?
Nobody is going to fix 98449. The ONE-line patchset fixing the issue was there
for YEARS. Why does it take so many years to revie
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108868
--- Comment #3 from Andrew Pinski ---
(In reply to Jakub Jelinek from comment #2)
> That would be invalid, vfork can't return from the containing function.
I messed up the if (it should be the opposite way around, that is checking for
non-zero)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107721
--- Comment #8 from Jerry DeLisle ---
FWIW : I think the typespec is being lost because the initial call into
gfc_match_array_constructor which finds and matches the typespec sets a local
variable seen_ts which is used later in that function to
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108846
--- Comment #5 from Giuseppe D'Angelo ---
> In the case of copy family algorithms, I believe it's OK to specially handle
> cases where last - first == 1.
https://github.com/gcc-mirror/gcc/blob/master/libstdc%2B%2B-v3/include/bits/stl_algobase.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108854
--- Comment #5 from Andrew Pinski ---
_ZThn20_N3tbb6detail2d114broadcast_nodeINS1_12continue_msgEE18register_successorERNS1_8receiverIS3_EE
demangles to:
non-virtual thunk to
tbb::detail::d1::broadcast_node::register_successor(tbb::detail::d1::
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108868
--- Comment #2 from Jakub Jelinek ---
That would be invalid, vfork can't return from the containing function.
Anyway, reduced testcase which shows the .ABNORMAL_DISPATCHER call in r13-5964
and none in r13-5965 in optimized is e.g. with just -O2
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108854
--- Comment #4 from Andrew Pinski ---
This is the ICE:
tbb-i686-linux> during RTL pass: expand
tbb-i686-linux> In file included from
/build/source/src/tbb/../../include/tbb/flow_graph.h:17,
tbb-i686-linux> from
/build/source/te
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108868
--- Comment #1 from Andrew Pinski ---
Here is a testcase which shows the removal of ABNORMAL_DISPATCHER though I am
not sure what is the best way to test if the removal makes a difference.
```
extern int vfork (void) __attribute__ ((__nothrow__
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108859
Jonathan Wakely changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Ever confirmed|0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108861
--- Comment #1 from Jonathan Wakely ---
Isn't this just Bug 98449? Why did you close that as FIXED?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108868
Jakub Jelinek changed:
What|Removed |Added
Target Milestone|--- |13.0
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108868
Bug ID: 108868
Summary: [13 Regression] ocaml-dune miscompilation on i686
since r13-5965
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108867
Bug ID: 108867
Summary: RFE: analyzer could suppress false positives by
detecting functions that are likely missing
__attribute__((noreturn))
Product: gcc
Versio
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108850
--- Comment #3 from anlauf at gcc dot gnu.org ---
(In reply to John Wingate from comment #2)
> I forgot to mention in the original description that the error does not
> occur if the SELECT CASE is removed.
Right. The testcase case be slightly r
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108865
--- Comment #3 from Andrew Pinski ---
(In reply to Costas Argyris from comment #2)
> (In reply to Andrew Pinski from comment #1)
> > Utf8 is the best generic solution really.
> > Using wmain is not very portable and the rest of gcc's sources can
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108865
--- Comment #2 from Costas Argyris ---
(In reply to Andrew Pinski from comment #1)
> Utf8 is the best generic solution really.
> Using wmain is not very portable and the rest of gcc's sources can't use
> wchar_t as that would break unix/Linux ha
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108850
--- Comment #2 from John Wingate ---
I forgot to mention in the original description that the error does not occur
if the SELECT CASE is removed.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108866
Andrew Pinski changed:
What|Removed |Added
Severity|normal |enhancement
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108866
Andrew Pinski changed:
What|Removed |Added
Component|c |target
--- Comment #1 from Andrew Pinsk
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108865
--- Comment #1 from Andrew Pinski ---
Utf8 is the best generic solution really.
Using wmain is not very portable and the rest of gcc's sources can't use
wchar_t as that would break unix/Linux handling.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108866
Bug ID: 108866
Summary: Allow to pass Windows resource file (.rc) as input to
gcc
Product: gcc
Version: 12.2.0
Status: UNCONFIRMED
Severity: normal
P
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108550
--- Comment #7 from Marek Polacek ---
We get the bogus error because we failed to deduce the auto in
constexpr auto is_pointer_v = is_pointer::value;
to bool.
We call do_auto_deduction and type_unification_real correctly deduces targs to
, but
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108862
Jakub Jelinek changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108865
Bug ID: 108865
Summary: gcc on Windows fails with Unicode path to source file
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Co
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108863
Andrew Pinski changed:
What|Removed |Added
Last reconfirmed||2023-02-20
Ever confirmed|0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108862
--- Comment #6 from CVS Commits ---
The master branch has been updated by Jakub Jelinek :
https://gcc.gnu.org/g:cd8b4fae52d02541c2d8bd2200caad3812f37368
commit r13-6147-gcd8b4fae52d02541c2d8bd2200caad3812f37368
Author: Jakub Jelinek
Date: M
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108864
Andrew Pinski changed:
What|Removed |Added
See Also||https://gcc.gnu.org/bugzill
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108864
Bug ID: 108864
Summary: Insufficient red zone in ASAN
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: sanitizer
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96025
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |anlauf at gcc dot
gnu.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108863
Andrew Pinski changed:
What|Removed |Added
Component|tree-optimization |rtl-optimization
--- Comment #1 from An
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108863
Thomas Koenig changed:
What|Removed |Added
Severity|normal |enhancement
Keywords|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108863
Bug ID: 108863
Summary: Unrolling could use range information
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: tree-op
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108834
--- Comment #10 from Martin Liška ---
I've filed an upstream review request:
https://reviews.llvm.org/D144424
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108850
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108848
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108847
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Keywords|ABI
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108243
--- Comment #9 from Patrick Palka ---
(In reply to Jiang An from comment #8)
> This seems a bug, not merely missing of optimization. The string_view object
> should always be statically initialized, because it has static storage
> duration and i
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108550
--- Comment #6 from Marek Polacek ---
Ah!
Started with
commit dc062b4986328bfeec3ebd744a9c116e28828bf0
Author: Jason Merrill
Date: Wed Aug 5 13:56:14 2015 -0400
re PR c++/66260 ([C++14] Failure to compile variable template with
recursi
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108550
--- Comment #5 from Andrew Pinski ---
(In reply to Marek Polacek from comment #4)
> Why is this a regression? I'm not finding a released version that compiled
> this.
The testcase in comment #2 works both with GCC 5.1.0 and 5.2.0 at least as o
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108550
Marek Polacek changed:
What|Removed |Added
CC||mpolacek at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101073
Marek Polacek changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101073
--- Comment #6 from CVS Commits ---
The trunk branch has been updated by Marek Polacek :
https://gcc.gnu.org/g:b2287a4d9a640fdc2caef6a067830ea65044deb7
commit r13-6145-gb2287a4d9a640fdc2caef6a067830ea65044deb7
Author: Marek Polacek
Date: We
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104921
Alex Coplan changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104921
--- Comment #8 from CVS Commits ---
The releases/gcc-10 branch has been updated by Alex Coplan
:
https://gcc.gnu.org/g:617377cc1641e4f63617b192e224bc96dfbbd324
commit r10-11222-g617377cc1641e4f63617b192e224bc96dfbbd324
Author: Alex Coplan
Dat
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96168
--- Comment #14 from Iain Sandoe ---
please see the Work In Progress here:
https://github.com/iains/gcc-darwin-arm64
this is a functional branch (although with known issues, since it is a
prototype)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108829
Marek Polacek changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108829
--- Comment #8 from CVS Commits ---
The releases/gcc-12 branch has been updated by Marek Polacek
:
https://gcc.gnu.org/g:12cdc0e266f02c3ba4e80c3d971463ff507e049b
commit r12-9191-g12cdc0e266f02c3ba4e80c3d971463ff507e049b
Author: Marek Polacek
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108834
--- Comment #9 from Martin Liška ---
(In reply to Jakub Jelinek from comment #8)
> Sure, we want to keep using libbacktrace. But libbacktrace can be extended
> if Ian is ok with it, or some extensions can be done on the
> libsanitizer/libbacktr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108829
Marek Polacek changed:
What|Removed |Added
Summary|[12/13 Regression] internal |[12 Regression] internal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108834
--- Comment #8 from Jakub Jelinek ---
Sure, we want to keep using libbacktrace. But libbacktrace can be extended if
Ian is ok with it, or some extensions can be done on the
libsanitizer/libbacktrace side of it.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108834
--- Comment #7 from Martin Liška ---
So clang uses __sanitizer::LLVMSymbolizer:
$ clang jhead.i -fsanitize=address -g && strace -f -s512 ./a.out 2>&1 | grep
execv
execve("./a.out", ["./a.out"], 0x7fffd520 /* 116 vars */) = 0
[pid 5529] exe
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108464
--- Comment #7 from Jakub Jelinek ---
The patches (3 variants) have been posted and are awaiting review. I've pinged
them twice.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106465
--- Comment #3 from Martin Uecker ---
Created attachment 54496
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=54496&action=edit
patch for C FE
Here is a patch.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108464
--- Comment #6 from Orion Poplawski ---
So, there was quite the initial flurry of activity here and then nothing. Any
chance we could get some more movement here? It's breaking a ccache test for
one. Thank you.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108862
--- Comment #5 from Jakub Jelinek ---
Created attachment 54495
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=54495&action=edit
gcc13-pr108862.patch
Variant patch, instead of creating another temporary and moving it we can just
do the hig
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108862
--- Comment #4 from Jakub Jelinek ---
Created attachment 54494
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=54494&action=edit
gcc13-pr108862.patch
Untested fix.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108862
--- Comment #3 from Segher Boessenkool ---
With -fno-unroll-loops added we get
foo:
.LFB0:
.cfi_startproc
cmpwi 0,3,0
ble 0,.L4
mtctr 3
addi 10,4,-8
addi 5,5,8
li 3,0
.p2align 4,,1
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108862
Jakub Jelinek changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |jakub at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104921
--- Comment #7 from CVS Commits ---
The releases/gcc-11 branch has been updated by Alex Coplan
:
https://gcc.gnu.org/g:ed3b4de8a648da4e574fb64344e90b6460946511
commit r11-10536-ged3b4de8a648da4e574fb64344e90b6460946511
Author: Alex Coplan
Dat
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108862
--- Comment #1 from Jakub Jelinek ---
Note, -O2 -mcpu=power9:
__attribute__((noipa)) unsigned __int128
foo (unsigned __int128 x, unsigned long long y, unsigned long long z)
{
return x + (unsigned __int128) y * z;
}
int
main ()
{
unsigned __
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108862
Jakub Jelinek changed:
What|Removed |Added
Ever confirmed|0 |1
Priority|P3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108862
Bug ID: 108862
Summary: [13 Regression] CryptX miscompilation on power9 since
r13-2107
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108829
--- Comment #6 from CVS Commits ---
The trunk branch has been updated by Marek Polacek :
https://gcc.gnu.org/g:02d8ab3e4e2f3d9dc12157a98c976d6698e71e29
commit r13-6141-g02d8ab3e4e2f3d9dc12157a98c976d6698e71e29
Author: Marek Polacek
Date: Th
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108856
Matthias Kretz (Vir) changed:
What|Removed |Added
Ever confirmed|0 |1
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98449
Vinícius dos Santos Oliveira changed:
What|Removed |Added
Status|SUSPENDED |RESOLVED
Resoluti
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108861
Bug ID: 108861
Summary: notify_all_at_thread_exit() should notify on cond
while lock is held to avoid a race
Product: gcc
Version: unknown
Status: UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108834
--- Comment #6 from Martin Liška ---
> so I wonder if emitting the locations isn't just wasted .rodata if libasan
> considers it being a windows_padding. In GCC 12 libsanitizer it was still
> location:
You are correct, we lost the ability to p
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98449
--- Comment #3 from Vinícius dos Santos Oliveira ---
LLVM's libcxx already applied this 1-line patchset:
https://github.com/llvm/llvm-project/commit/64fc3cd55d586498dd21c5b3cfaa755793913772
Can we have the same here on GCC side (I've already sub
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108772
--- Comment #6 from Richard Biener ---
(In reply to Richard Biener from comment #5)
> another possibility would be to stream "no DIE" info for not late
> created decls
like by setting DECL_IGNORED_P on them? Like maybe with the following
which
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108835
Gaius Mulley changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108860
Bug ID: 108860
Summary: New (since gcc 12) false positive null-dereference in
vector.resize
Product: gcc
Version: 12.2.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108859
Bug ID: 108859
Summary: Exception thrown by std::filesystem::copy() is wrong
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108854
--- Comment #3 from Jonathan Wakely ---
(In reply to davidak from comment #0)
> I don't know how to get the "preprocessed file (*.i*) that triggers the
> bug", but otherwise you should have all requested information.
Unfortunately that's the mo
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108793
--- Comment #3 from Richard Biener ---
It's caused by -1 -A -> ~A being invoked from number_of_iterations_until_wrap:
1497 num = fold_build2 (MINUS_EXPR, niter_type, wide_int_to_tree
(type, max),
1498 iv1->b
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108804
Richard Biener changed:
What|Removed |Added
Target||x86_64-*-*
Status|UNCONFIR
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108339
Kito Cheng changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108339
--- Comment #4 from CVS Commits ---
The releases/gcc-10 branch has been updated by Kito Cheng :
https://gcc.gnu.org/g:951ca35bdbbde7bb348337d7db3919c4a0628e25
commit r10-11221-g951ca35bdbbde7bb348337d7db3919c4a0628e25
Author: Nelson Chu
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108858
Bug ID: 108858
Summary: Assert_Failure at exp_ch6.adb:6499
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: ada
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108816
Richard Biener changed:
What|Removed |Added
Known to work||13.0
Priority|P3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108816
--- Comment #3 from CVS Commits ---
The master branch has been updated by Richard Biener :
https://gcc.gnu.org/g:63471c5008819bbf6ec32a6f4d8701fe57b96fa9
commit r13-6140-g63471c5008819bbf6ec32a6f4d8701fe57b96fa9
Author: Richard Biener
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107931
--- Comment #17 from rguenther at suse dot de ---
On Mon, 20 Feb 2023, jakub at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107931
>
> --- Comment #16 from Jakub Jelinek ---
> As discussed elsewhere, always_inline is
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94908
--- Comment #6 from Hongtao.liu ---
Yes, insertps can select any element from src and insert into any place of the
dest. under sse4.1, x86 can generate
vinsertps xmm0, xmm1, xmm0, 64 # xmm0 = xmm0[1],xmm1[1,2,3]
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108843
Richard Biener changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108854
Bug ID: 108854
Summary: tbb-2021.8.0 fails on i686-linux (32-bit)
Product: gcc
Version: 11.3.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
1 - 100 of 145 matches
Mail list logo
