Hi,
Currently move_max follows the tuning feature first, but ideally it
should sync with prefer-vector-width when it is explicitly set to keep
vector move and operation with same vector size.
Bootstrapped/regtested on x86-64-pc-linux-gnu{-m32,}
OK for trunk?
gcc/ChangeLog:
PR
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112986
Andreas Krebbel changed:
What|Removed |Added
CC||shinwogud12 at gmail dot com
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112665
Andreas Krebbel changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112387
JuzheZhong changed:
What|Removed |Added
Resolution|--- |FIXED
Status|NEW
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112387
--- Comment #3 from GCC Commits ---
The master branch has been updated by Pan Li :
https://gcc.gnu.org/g:e9f0af150358d93b4c4c5f65d662748ae87bd3d0
commit r14-6533-ge9f0af150358d93b4c4c5f65d662748ae87bd3d0
Author: Juzhe-Zhong
Date: Thu Dec
After recent RVV cost model tweak, I found this PR issue has been fixed.
Add testcase and committed.
PR target/112387
gcc/testsuite/ChangeLog:
* gcc.dg/vect/costmodel/riscv/rvv/pr112387.c: New test.
---
.../vect/costmodel/riscv/rvv/pr112387.c | 19 +++
1
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110606
--- Comment #11 from Jeevitha ---
Regarding the test case provided by Matthias Klose:
Within the AllocMemory() routine, the compiler aimed to eliminate the entire if
block but faced difficulties in removing references to the variable
The implementation of this patch has some issues. When I compile 521.wrf
with -Ofast -mlasx -flto -muse-movcf2gr, it results in an ICE:
during RTL pass: reload
module_mp_fast_sbm.fppized.f90: In function 'fast_sbm.constprop':
module_mp_fast_sbm.fppized.f90:1369:25: internal compiler error:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110640
--- Comment #9 from GCC Commits ---
The master branch has been updated by Richard Biener :
https://gcc.gnu.org/g:9e20779a7d8e14e77df6efaeadc6bf3a001336ef
commit r14-6532-g9e20779a7d8e14e77df6efaeadc6bf3a001336ef
Author: Richard Biener
Date:
Pushed.
PR tree-optimization/110640
* gcc.dg/torture/pr110640.c: New testcase.
---
gcc/testsuite/gcc.dg/torture/pr110640.c | 22 ++
1 file changed, 22 insertions(+)
create mode 100644 gcc/testsuite/gcc.dg/torture/pr110640.c
diff --git
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110640
Richard Biener changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Known to work|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112986
Andreas Krebbel changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
Hi!
On top of the previously posted patch, this simplifies say (x * 16) / (x * 4)
into 4. Unlike the previous pattern, this is something we didn't fold
previously on GENERIC, so I think it shouldn't be all wrapped with #if
GIMPLE. The question whether there should be fold_overflow_warning for
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110640
Richard Biener changed:
What|Removed |Added
Known to work||14.0
Summary|[13/14
Hi!
The following testcase is optimized just on GENERIC (using
strict_overflow_p = false;
if (TREE_CODE (arg1) == INTEGER_CST
&& (tem = extract_muldiv (op0, arg1, code, NULL_TREE,
_overflow_p)) != 0)
{
if
Hi Richard,
Thanks a lot for your response!
Another failure reported by the Linaro CI is as follows:
Running gcc:gcc.dg/dg.exp ...
FAIL: gcc.dg/ira-shrinkwrap-prep-1.c scan-rtl-dump pro_and_epilogue "Performing
shrink-wrapping"
FAIL: gcc.dg/pr10474.c scan-rtl-dump pro_and_epilogue "Performing
On Wed, Nov 29, 2023 at 11:43:05AM +, Julian Brown wrote:
> * c-c++-common/gomp/target-enter-data-1.c: Adjust scan output.
struct bar { int num_vectors; double *vectors; };
is 16 bytes only on 64-bit targets, on 32-bit ones it is just 8 bytes,
so the explicit matching of the * 16
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112968
Jakub Jelinek changed:
What|Removed |Added
Resolution|--- |FIXED
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112904
--- Comment #5 from GCC Commits ---
The master branch has been updated by Jakub Jelinek :
https://gcc.gnu.org/g:585dc19ef051959d688e6ea89b41998600480ecb
commit r14-6530-g585dc19ef051959d688e6ea89b41998600480ecb
Author: Jakub Jelinek
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112968
--- Comment #4 from GCC Commits ---
The master branch has been updated by Jakub Jelinek :
https://gcc.gnu.org/g:7ff33c609a64319583223d6d39a89e971f993ecf
commit r14-6529-g7ff33c609a64319583223d6d39a89e971f993ecf
Author: Jakub Jelinek
Date:
Committed, thanks Kito.
Pan
From: Kito Cheng
Sent: Thursday, December 14, 2023 2:45 PM
To: Juzhe-Zhong
Cc: GCC Patches ; Kito Cheng ;
Jeff Law ; Robin Dapp
Subject: Re: [PATCH] RISC-V: Add RVV builtin vectorization cost model
LGTM
Juzhe-Zhong mailto:juzhe.zh...@rivai.ai>> 於 2023年12月14日
週四
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53
JuzheZhong changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53
--- Comment #6 from GCC Commits ---
The master branch has been updated by Pan Li :
https://gcc.gnu.org/g:5e0f67b84a615ba186ab234a9bc43df0df5a50b6
commit r14-6528-g5e0f67b84a615ba186ab234a9bc43df0df5a50b6
Author: Juzhe-Zhong
Date: Thu Dec
LGTM
Juzhe-Zhong 於 2023年12月14日 週四 11:24 寫道：
> This patch fixes PR11153:
>
> ble a1,zero,.L8
> addiw a5,a1,-1
> li a4,4
> addisp,sp,-16
> mv a2,a0
> sext.w a3,a1
> bleua5,a4,.L9
> srliw a4,a3,2
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112986
--- Comment #5 from 김대영 <22s302h0659 at sonline20 dot sen.go.kr> ---
Thank you for your response. Naturally, I anticipated that the issue might be
with the s390x architecture cross-compiler. However, unexpectedly, I was
unaware that qemu was
Florian Weimer via Gcc writes:
> [...]
> On other architectures with support for GNU2 TLS descriptors, those are
> used by default.
>
It looks like arm32 defaults to gnu, not gnu2. andrew mentioned fdpic
will be an issue there but maybe we could carve that out.
> Should we flip the default
On 2023/12/12 07:43 UTC+8, Jeff Law via Gcc wrote:
On 12/11/23 16:19, Andrew Pinski via Gcc wrote:
nds32 support in Linux was removed last year:
https://www.phoronix.com/news/Andes-Tech-NDS32-Removal
The support for glibc never made it upstream as far as I can tell either.
What are others
On 2023/12/12 07:43 UTC+8, Jeff Law via Gcc wrote:
On 12/11/23 16:19, Andrew Pinski via Gcc wrote:
nds32 support in Linux was removed last year:
https://www.phoronix.com/news/Andes-Tech-NDS32-Removal
The support for glibc never made it upstream as far as I can tell either.
What are others
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113016
Bug ID: 113016
Summary: -mtls-dialect=gnu2 conflicts with -mfdpic but ICEs
rather than gives an error
Product: gcc
Version: 14.0
Status: UNCONFIRMED
On Wed, Dec 13, 2023 at 1:08 PM Andrew Pinski wrote:
>
> On Wed, Dec 13, 2023 at 6:19 AM Florian Weimer via Gcc
> wrote:
> >
> > I feel like I have asked this before. Currently, GCC uses calls to
> > __tls_get_addr to obtain the address of global-dynamic TLS variables.
> > On other
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113015
Bug ID: 113015
Summary: ICE: verify_ssa failed: definition in block 12 does
not dominate use in block 13 at -O with _BitInt()
Product: gcc
Version: 14.0
Status:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113014
--- Comment #1 from JuzheZhong ---
Richard S has a late combine PASS which is going to be merged in GCC-14.
Since we generate this following RTL int split1:
(insn 48 24 49 5 (set (reg:SI 149)
(const_int 0 [0])) -1
(nil))
(insn
I prefer all vector related function registration should be in the same
function groups.
like aarch64:
/* A list of all SVE ACLE functions. */
static CONSTEXPR const function_group_info function_groups[] = {
#define DEF_SVE_FUNCTION_GS(NAME, SHAPE, TYPES, GROUPS, PREDS) \
{ #NAME, ::NAME,
This patch fixes PR11153:
ble a1,zero,.L8
addiw a5,a1,-1
li a4,4
addisp,sp,-16
mv a2,a0
sext.w a3,a1
bleua5,a4,.L9
srliw a4,a3,2
sllia4,a4,4
mv a5,a0
add a4,a4,a0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113013
--- Comment #3 from Andrew Pinski ---
The use of __alloc_size__ here is definitely not well defined but GCC should
NOT crash.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113013
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |12.4
--- Comment #2 from Andrew Pinski
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113014
Bug ID: 113014
Summary: RISC-V: Redundant zeroing instructions in reduction
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113013
Andrew Pinski changed:
What|Removed |Added
Ever confirmed|0 |1
Keywords|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113012
Andrew Pinski changed:
What|Removed |Added
See Also||https://gcc.gnu.org/bugzill
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113013
Bug ID: 113013
Summary: [12/13/14 regression] ICE in fold_convert_loc with
-fsanitize=undefined
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113012
--- Comment #3 from Andrew Pinski ---
Note once we remove the -1, GCC does not ICE. I am 99% sure it is undefined to
go one before the begining of the array, only one past the end of the array is
well defined.
Note I am not shocked that xorg
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113012
--- Comment #2 from Andrew Pinski ---
(In reply to Andrew Pinski from comment #1)
> Note I am not 100% sure the above code is well defined due to subtracting
> one from the allocated array.
and yes this represents exactly what the code does.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113012
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Ever confirmed|0
Hi all,
According to ISE050 published at the end of September, RAO-INT will not
be in Grand Ridge anymore. This patch aims to remove it.
The documentation comes following:
https://cdrdv2.intel.com/v1/dl/getContent/671368
Regtested on x86_64-pc-linux-gnu. Ok for trunk and backport to GCC13?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112871
Patrick O'Neill changed:
What|Removed |Added
CC||jeffreyalaw at gmail dot com
---
On Linux/x86_64,
5fdb150cd4bf8f2da335e3f5c3a17aafcbc66dbe is the first bad commit
commit 5fdb150cd4bf8f2da335e3f5c3a17aafcbc66dbe
Author: Julian Brown
Date: Mon Aug 14 12:41:56 2023 +
OpenMP/OpenACC: Rework clause expansion and nested struct handling
caused
FAIL:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113001
--- Comment #1 from Patrick O'Neill ---
Bisected to r14-3041-g18c453f0e63
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113012
Andrew Pinski changed:
What|Removed |Added
Keywords||ice-on-valid-code
Target
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113012
Bug ID: 113012
Summary: [14 regression] ICE when building xorg-server with
-fsanitize=undefined
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity:
On 2023/12/14 4:52, Thomas Schwinge wrote:
> Hi Lipeng!
>
> On 2023-12-12T02:05:26+, "Zhu, Lipeng" wrote:
> > On 2023/12/12 1:45, H.J. Lu wrote:
> >> On Sat, Dec 9, 2023 at 7:25 PM Zhu, Lipeng
> wrote:
> >> > On 2023/12/9 23:23, Jakub Jelinek wrote:
> >> > > On Sat, Dec 09, 2023 at
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112997
--- Comment #7 from cqwrteur ---
(In reply to Andrew Pinski from comment #5)
> (In reply to cqwrteur from comment #4)
> > (In reply to Andrew Pinski from comment #1)
> > > Why are you building libstdc++ sources with clang? I doubt that is
> >
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113011
--- Comment #4 from Andrew Pinski ---
C23 working draft can be found at
https://open-std.org/JTC1/SC22/WG14/www/docs/n3096.pdf .
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113011
Andrew Pinski changed:
What|Removed |Added
Resolution|--- |INVALID
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113011
--- Comment #2 from Andrew Pinski ---
>From C99 draft: 5.1.2.2.1 Program startup
The function called at program startup is named main.The implementation
declares no prototype for this function. It shall be defined with a return type
ofintand
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113011
--- Comment #1 from Andrew Pinski ---
clang even errors out:
:6:1: error: 'main' must return 'int'
6 | enum E main(){}
| ^~
| int
On 11/27/23 10:58, Patrick Palka wrote:
gcc/cp/ChangeLog:
* cp-tree.h (type_targs_deducible_from): Adjust return type.
* pt.cc (alias_ctad_tweaks): Handle C++23 inherited CTAD.
(inherited_ctad_tweaks): Define.
(type_targs_deducible_from): Return the deduced
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113011
Bug ID: 113011
Summary: main declared with enumerated type is not accepted
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
On 12/13/23 19:00, Marek Polacek wrote:
On Wed, Dec 13, 2023 at 11:47:37AM -0500, Jason Merrill wrote:
Tested x86_64-pc-linux-gnu, applying to trunk.
-- 8< --
When building an AGGR_INIT_EXPR from a CALL_EXPR, we shouldn't lose location
information.
I think the following should be an obvious
From: Vladimir Mezentsev
This is fixes for releases/gcc-13 for 31109 gprofng not built and installed in
a combined binutils+gcc build
I only cherry-picked 24552056fd5fc677c0d032f54a5cad1c4303d312 and tested my
build.
ChangeLog:
* Makefile.def: Add gprofng module.
*
On Wed, Dec 13, 2023 at 7:59 PM Jakub Jelinek wrote:
>
> On Fri, Dec 08, 2023 at 03:12:00PM +0800, liuhongt wrote:
> > Bootstrapped and regtested on x86_64-pc-linux-gnu{-m32,}.
> > Ready push to trunk.
> >
> > gcc/ChangeLog:
> >
> > PR target/112904
> > * config/i386/mmx.md
在 2023/12/13 下午9:20, Xi Ruoyao 写道:
On Wed, 2023-12-13 at 20:22 +0800, chenglulu wrote:
在 2023/12/10 上午1:03, Xi Ruoyao 写道:
Replace the instruction costs in loongarch_rtx_cost_data constructor
based on micro-benchmark results on LA464 and LA664.
This allows optimizations like "x * 17" to alsl,
Tested x86_64-linux.
Does this look right? Can we do it faster, or simplify it?
-- >8 --
This reduces the overhead of using std::is_trivially_destructible_v and
as a result fixes some recent regressions seen with a non-default
GLIBCXX_TESTSUITE_STDS env var:
FAIL: 20_util/variant/87619.cc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113009
--- Comment #4 from Edwin Lu ---
(In reply to JuzheZhong from comment #3)
> (In reply to Edwin Lu from comment #2)
> > Re-bisected to r14-6197-g2e7abd09621
> >
> > Full steps to reproduce:
> > mkdir dump1
> > ./build-gcc-linux-stage2/gcc/xgcc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113007
Jonathan Wakely changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113007
--- Comment #2 from Jonathan Wakely ---
(In reply to Pavel Novikov from comment #0)
> e.g. for `std::variant` the overload
> set would be
>
> void F(std::monostate) {}
> void F(bool) {}
> void F(int64_t) {}
> void F(double) {}
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113009
--- Comment #3 from JuzheZhong ---
(In reply to Edwin Lu from comment #2)
> Re-bisected to r14-6197-g2e7abd09621
>
> Full steps to reproduce:
> mkdir dump1
> ./build-gcc-linux-stage2/gcc/xgcc -B./build-gcc-linux-stage2/gcc/
> -march=rv64gcv
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112997
--- Comment #6 from Jonathan Wakely ---
I think we can just change the declaration in unwind-cxx.h
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113009
Edwin Lu changed:
What|Removed |Added
CC||juzhe.zhong at rivai dot ai
--- Comment #2
On 12/13/23 02:03, Christoph Müllner wrote:
On Wed, Dec 13, 2023 at 9:22 AM Liao Shihua wrote:
In Scalar Crypto Built-In functions, some require immediate parameters,
But register_operand are incorrectly used in the pattern.
E.g.:
__builtin_riscv_aes64ks1i(rs1,1)
Before:
li
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112468
--- Comment #11 from Hans-Peter Nilsson ---
(In reply to Tamar Christina from comment #10)
> Hi,
>
> It's not forgotten. I've agreed on a fix with the maintainers that should
> solve a bunch of other (older) issues with copysign as well.
>
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112997
Andrew Pinski changed:
What|Removed |Added
Status|WAITING |RESOLVED
Resolution|---
The alpha port recently failed its weekly test due to a lack of a
prototype for the syscall() routine. Fixed thusly and pushed to the trunk.
Jeff
commit acfd33620af3519b84baecedb0eb6618c2f599a6
Author: Jeff Law
Date: Wed Dec 13 17:24:39 2023 -0700
[committed] Minor testsuite fallout
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80283
--- Comment #38 from Andrew Pinski ---
For aarch64, the test from comment #11 is so much worse on the trunk than in
GCC 13.2.0.
On Wed, Dec 13, 2023 at 11:47:37AM -0500, Jason Merrill wrote:
> Tested x86_64-pc-linux-gnu, applying to trunk.
>
> -- 8< --
>
> When building an AGGR_INIT_EXPR from a CALL_EXPR, we shouldn't lose location
> information.
I think the following should be an obvious fix, so I'll check it in.
--
Alex Coplan writes:
> This patch uses the new force_reload_address routine added by the
> previous patch to fix PR112906.
>
> Bootstrapped/regtested on aarch64-linux-gnu, OK for trunk?
OK, thanks, and sorry for the breakage.
Richard
>
> Thanks,
> Alex
>
> gcc/ChangeLog:
>
> PR
Alex Coplan writes:
> Hi,
>
> In PR112906 we ICE because we try to use force_reg to reload an
> auto-increment address, but force_reg can't do this.
>
> With the aim of fixing the PR by supporting reloading arbitrary
> addresses in pre-RA splitters, this patch generalizes
>
Thanks for the update. The new comments are really nice, and I think
make the implementation much easier to follow.
I was going to say OK with the changes below, but there's one question/
comment near the end about the double list walk.
Alex Coplan writes:
> +// Convenience wrapper around
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112997
--- Comment #4 from cqwrteur ---
(In reply to Andrew Pinski from comment #1)
> Why are you building libstdc++ sources with clang? I doubt that is supported.
GCC does not support WebAssembly backend
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112758
Andrew Pinski changed:
What|Removed |Added
CC||gkm at rivosinc dot com
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113010
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113009
--- Comment #1 from Edwin Lu ---
Found issue with bisection script. Currently re-bisecting
On 11/24/23 3:28 AM, Kewen.Lin wrote:
>> + int regoff = INTVAL (operands[2]) * GET_MODE_SIZE (V16QImode);
>
> Is it intentional to keep GET_MODE_SIZE (V16QImode) instead of 16?
> I think if one day NUM_POLY_INT_COEFFS isn't 1 on rs6000 any more,
> we have to add one explicit .to_constant ()
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113010
Bug ID: 113010
Summary: [RISCV] sign-extension lost in comparison with
constant embedded in comma-op expression
Product: gcc
Version: 13.0
Status: UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113009
Bug ID: 113009
Summary: [14] RISC-V: gcc.c-torture/unsorted/dump-noaddr.c
flakey tests
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
tly evaluates to false).
Declaring v2 fails to compile entirely:
opt/compiler-explorer/gcc-trunk-20231213/include/c++/14.0.0/type_traits:3284:7:
required from 'constexpr const bool
std::is_trivially_default_constructible_v >'
3284 | = __is_trivially_constructib
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113007
--- Comment #1 from Andrew Pinski ---
Created attachment 56874
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56874=edit
Full testcase
Please next time attach the full testcase (or place it inline) instead of just
linking to godbolt.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113007
Bug ID: 113007
Summary: `std::variant` converting constructor and `operator=`
compile while the C++ Standard says they must not
Product: gcc
Version: 13.2.1
Status:
On Wed, Dec 13, 2023 at 6:19 AM Florian Weimer via Gcc wrote:
>
> I feel like I have asked this before. Currently, GCC uses calls to
> __tls_get_addr to obtain the address of global-dynamic TLS variables.
> On other architectures with support for GNU2 TLS descriptors, those are
> used by
Clean up scan dump failures on linux rv64 vector targets Juzhe mentioned
could be ignored for now. This will help reduce noise and make it more obvious
if a bug or regression is introduced. The failures that are still reported
are either execution failures or failures that are also present on
On Wed, 13 Dec 2023 at 20:56, Thomas Schwinge wrote:
>
> Hi!
>
> On 2023-12-13T20:27:44+, Jonathan Wakely wrote:
> > On Wed, 13 Dec 2023, 19:37 Thomas Schwinge, wrote:
> >> On 2023-12-13T11:15:54-0800, Jerry D via Gcc wrote:
> >> > I am getting this failure to build from clean trunk.
> >>
This patch uses the new force_reload_address routine added by the
previous patch to fix PR112906.
Bootstrapped/regtested on aarch64-linux-gnu, OK for trunk?
Thanks,
Alex
gcc/ChangeLog:
PR target/112906
* config/aarch64/aarch64-sve.md (@aarch64_vec_duplicate_vq_le):
Use
Hi,
In PR112906 we ICE because we try to use force_reg to reload an
auto-increment address, but force_reg can't do this.
With the aim of fixing the PR by supporting reloading arbitrary
addresses in pre-RA splitters, this patch generalizes
lra-constraints.cc:emit_inc and makes it available to the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101603
Bug 101603 depends on bug 93740, which changed state.
Bug 93740 Summary: Template base classes parametrized by pointer-to-member are
amibiguous
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93740
What|Removed
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93740
Patrick Palka changed:
What|Removed |Added
Resolution|--- |FIXED
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55004
Bug 55004 depends on bug 93740, which changed state.
Bug 93740 Summary: Template base classes parametrized by pointer-to-member are
amibiguous
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93740
What|Removed
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99186
--- Comment #7 from GCC Commits ---
The master branch has been updated by Patrick Palka :
https://gcc.gnu.org/g:35ba3add7d0a9fc6ce955ba8ad82b0413e86ad7d
commit r14-6520-g35ba3add7d0a9fc6ce955ba8ad82b0413e86ad7d
Author: Patrick Palka
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104867
--- Comment #2 from GCC Commits ---
The master branch has been updated by Patrick Palka :
https://gcc.gnu.org/g:35ba3add7d0a9fc6ce955ba8ad82b0413e86ad7d
commit r14-6520-g35ba3add7d0a9fc6ce955ba8ad82b0413e86ad7d
Author: Patrick Palka
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93740
--- Comment #6 from GCC Commits ---
The master branch has been updated by Patrick Palka :
https://gcc.gnu.org/g:c822ad86984e752734b9c371f9cfef9330334ec4
commit r14-6519-gc822ad86984e752734b9c371f9cfef9330334ec4
Author: Patrick Palka
Date:
Hi!
On 2023-12-13T20:27:44+, Jonathan Wakely wrote:
> On Wed, 13 Dec 2023, 19:37 Thomas Schwinge, wrote:
>> On 2023-12-13T11:15:54-0800, Jerry D via Gcc wrote:
>> > I am getting this failure to build from clean trunk.
>>
>> This is due to commit
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113006
Bug ID: 113006
Summary: OpenMP 5 - lvalue parsing support for map/to/from
clause
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
1 - 100 of 302 matches
Mail list logo
