https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111086
--- Comment #1 from Andrew Pinski ---
if (STRICT_ALIGNMENT)
warning (OPT_Wpacked, "packed attribute causes inefficient "
"alignment for %qE", name);
else
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111086
Bug ID: 111086
Summary: Possibly incorrect warning: arm-none-eabi-gcc:packed
attribute causes inefficient alignment for
Product: gcc
Version: 9.2.1
Status: UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111002
Andrew Pinski changed:
What|Removed |Added
Keywords||patch
URL|
Like convert we can sink view_convert into vec_cond but
we can only do it if the element types are nop_conversions.
This is to allow conversion between signed and unsigned types only.
Rather than between integer and float types which mess up the vec_cond
so that isel does not understand `a?-1:0`
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111084
--- Comment #6 from Xi Ruoyao ---
(In reply to Andrew Pinski from comment #5)
> Also buildroot uses sysroots and chroot/containers instead.
>
> Containers/chroot is the better approach anyways.
We use sysroot and chroot since Linux From
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111084
--- Comment #5 from Andrew Pinski ---
Also buildroot uses sysroots and chroot/containers instead.
Containers/chroot is the better approach anyways.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111084
Xi Ruoyao changed:
What|Removed |Added
CC||xry111 at gcc dot gnu.org
--- Comment #4
---
htdocs/gcc-14/changes.html | 4
1 file changed, 4 insertions(+)
diff --git a/htdocs/gcc-14/changes.html b/htdocs/gcc-14/changes.html
index eae25f1a..2c888660 100644
--- a/htdocs/gcc-14/changes.html
+++ b/htdocs/gcc-14/changes.html
@@ -151,6 +151,10 @@ a work-in-progress.
This patch refactors the Phase 3 (Demand fusion) and rename it into Earliest
fusion.
I do the refactor for the following reasons:
1. Current implementation of phase 3 is doing too many things which makes the
code quality
quite messy and not easy to maintain.
2. The demand fusion I do
Jeff,
Thanks a lot for your comments.
The widen shift mode is on i1/i2 before they're combined with i3 to newpat.
The newpat matches rotate/mask pattern. The i1/i2 itself don't match
rotate/mask pattern.
I did an experiment to disable widen shift mode for
lshiftrt. I tested it on
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102609
--- Comment #13 from waffl3x ---
I am finding myself realizing that implementing this as a member function and
turning off member function bits seems to be more difficult than implementing
it as a static function and implementing member
gcc/ChangeLog:
* ada/Makefile.rtl: Add LoongArch support.
* ada/libgnarl/s-linux__loongarch.ads: New.
* ada/libgnat/system-linux-loongarch.ads: New.
* config/loongarch/loongarch.h: mark normalized options
passed from driver to gnat1 as explicit for
On Sun, Aug 20, 2023 at 6:44 AM ZiNgA BuRgA via Gcc-patches
wrote:
>
> Hi,
>
> With the proposed design of these switches, how would I restrict AVX10.1
> to particular AVX-512 subsets?
We can't, avx10.1 is taken as an indivisible ISA which contains all
AVX512 related instructions.
> We’ve been
I am so sorry sending the wrong and duplicate patch.
Forget about this patch.
This patch exports 'compute_antinout_edge' and 'compute_earliest' as global
scope
which is going to be used in VSETVL PASS of RISC-V backend.
The demand fusion is the fusion of VSETVL information to emit VSETVL which
dominate and pre-config for most
of the RVV instructions in order to elide
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111062
--- Comment #1 from Hongtao.liu ---
(In reply to Zdenek Sojka from comment #0)
> Created attachment 55755 [details]
> reduced testcase
>
> Compiler output:
> $ x86_64-pc-linux-gnu-gcc -O -mavx10.1-256 -mavx512bw -mno-avx512f testcase.c
> cc1:
void foo(_Float16 y, int64_t *i64p)
{
vint64m1_t vx =__riscv_vle64_v_i64m1 (i64p, 1);
vx = __riscv_vadd_vv_i64m1 (vx, vx, 1);
vfloat16m1_t vy =__riscv_vfmv_s_f_f16m1 (y, 1);
asm volatile ("# use %0 %1" : : "vr"(vx), "vr" (vy));
}
zve64f:
foo:
vsetivlizero,1,e16,mf4,ta,ma
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111002
--- Comment #2 from Andrew Pinski ---
here is the corrected patch:
diff --git a/gcc/match.pd b/gcc/match.pd
index 851f1af6eac..81666f28465 100644
--- a/gcc/match.pd
+++ b/gcc/match.pd
@@ -4718,6 +4718,15 @@ DEFINE_INT_AND_FLOAT_ROUND_FN (RINT)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111082
Andrew Pinski changed:
What|Removed |Added
Last reconfirmed||2023-08-20
Snapshot gcc-14-20230820 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/14-20230820/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 14 git branch
with the following options: git://gcc.gnu.org/git/gcc.git branch
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111085
Gaius Mulley changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111085
--- Comment #2 from CVS Commits ---
The master branch has been updated by Gaius Mulley :
https://gcc.gnu.org/g:a724c6e93dfce3a86f9c0fbf8be4316c37dd5a40
commit r14-3346-ga724c6e93dfce3a86f9c0fbf8be4316c37dd5a40
Author: Gaius Mulley
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108143
--- Comment #5 from CVS Commits ---
The master branch has been updated by Gaius Mulley :
https://gcc.gnu.org/g:a724c6e93dfce3a86f9c0fbf8be4316c37dd5a40
commit r14-3346-ga724c6e93dfce3a86f9c0fbf8be4316c37dd5a40
Author: Gaius Mulley
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111085
Gaius Mulley changed:
What|Removed |Added
Last reconfirmed||2023-08-20
Ever confirmed|0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111085
Bug ID: 111085
Summary: nexttoward and nexttowardf have incorrect definitions
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Committed as obvious, making gcc.dg/darwin-minversion-link.c pass on macOS 13
and 14 (darwin22 and darwin23, respectively).
FX
0001-Testsuite-darwin-account-for-macOS-13-and-14.patch
Description: Binary data
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111084
--- Comment #3 from Henrique ---
Hello, the reason is that linux from scratch bootstraps an initial toolchain
decoupled from the host toolchain before installing the final system. The final
installation will use the correct paths. The initial
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111084
Andrew Pinski changed:
What|Removed |Added
Status|WAITING |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=52556
Andrew Pinski changed:
What|Removed |Added
CC||hdante at gmail dot com
--- Comment #7
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111084
Andrew Pinski changed:
What|Removed |Added
Ever confirmed|0 |1
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111084
Bug ID: 111084
Summary: Support configurable dynamic linker path
Product: gcc
Version: 13.2.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107761
--- Comment #2 from gnzlbg ---
Update: the reference implementation is now merged into libc++ and will release
with LLVM 17.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=49588
anlauf at gcc dot gnu.org changed:
What|Removed |Added
CC||anlauf at gcc dot gnu.org
Hi,
testsuite/libgomp.c/simd-math-1.c calls nonstandard functions that are not
available on darwin (and possibly other systems?). Because I did not want to
disable their testing completely, I suggest we simply use preprocessor macros
to avoid them on darwin.
This fixes the test failure on
Hello Thiago,
On 18.08.23 23:24, Thiago Jung Bauermann wrote:
Tobias Burnus writes:
the patch looks good to me. Thanks! Can you commit the patch yourself or
do you need someone to do this for you?
Thank you! I don't have commit access, so I would need someone to do
this for me.
Done now
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110756
Tobias Burnus changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110756
--- Comment #5 from CVS Commits ---
The master branch has been updated by Tobias Burnus :
https://gcc.gnu.org/g:40a6803c6d8ca244a7bdda8e4ec986c418362b24
commit r14-3344-g40a6803c6d8ca244a7bdda8e4ec986c418362b24
Author: Thiago Jung Bauermann
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110919
--- Comment #5 from Andrew Pinski ---
Or take:
```
_Bool g(int a, int b)
{
b &= 1;
_Bool t = a == b;
_Bool e = a != 0;
_Bool g = t & e;
return g;
}
int g0(int a, int b)
{
b &= 1;
_Bool t = 1 == b;
_Bool e = a == 1;
_Bool g = t
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110919
Andrew Pinski changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned
Committed as obvious, fixing three more darwin-specific failures in analyzer
testsuite.
This fixes:
FAIL: gcc.dg/plugin/taint-CVE-2011-0521-5.c
-fplugin=./analyzer_kernel_plugin.so (test for warnings, line 39)
FAIL: gcc.dg/plugin/taint-CVE-2011-0521-6.c
Hi,
> IMO, changes like this qualify as obvious, so I’d go ahead (thanks for this
> test fail triage)
Makes sense. I’ve committed, as well as another one, attached, slightly
amending the expected pattern of a sarif plugin test.
FX
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111082
Andrew Pinski changed:
What|Removed |Added
Summary|ICE in |[14 Regression] ICE in
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111081
--- Comment #1 from Iain Sandoe ---
This seems likely related to whether we consider type info to be weak linkage.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111083
--- Comment #1 from Iain Sandoe ---
since this is a scan-dump test, we do not need to execute it - I guess we could
add "-fno-PIE" to the options - AFAIR we will only reject this when linking.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111083
Francois-Xavier Coudert changed:
What|Removed |Added
Last reconfirmed||2023-08-20
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111083
Bug ID: 111083
Summary: Test failure of g++.dg/ipa/pr67056.C on darwin
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component:
Partial vector src is forced to a register as ops[1], we can use it
instead of SRC in the call to ix86_expand_sse_cmp. This change avoids
forcing operand[1] to a register in sign/zero-extend expanders.
gcc/ChangeLog:
* config/i386/i386-expand.cc (ix86_expand_sse_extend): Use ops[1]
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102609
--- Comment #12 from Gašper Ažman ---
Replies to relevant snippets inline.
That was quite a write-up!
> The only compelling case I can think of for such a thing would be passing a
> pointer type that isn't related by inheritance anyway. That
Hi FX,
> On 20 Aug 2023, at 13:15, FX Coudert via Gcc-patches
> wrote:
> The fact that this test needs alias support was indicated in
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85656 but never committed.
> Without it, the test fails on darwin.
>
> OK to commit?
IMO, changes like this
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111082
--- Comment #1 from Manuel Lauss ---
Created attachment 55767
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=55767=edit
another compressed unreduced testcase
Another testcase. it triggers with "-march=zvner1" but not e.g. "core2" but
ced testcase
gcc version 14.0.0 20230820 (experimental)
d77c280454cfba48ef38357145cecdabc8c1b05c
# gcc -O2 -march=znver4 -mtune=znver4 -pipe -std=gnu++11 gcc14-bf.ii
In file included from
/tmp-ram/portage/media-gfx/hugin-2022.0.0/work/hugin-2022.0.0/src/hugin_base/panodata/PanoramaData.h
Hi,
The fact that this test needs alias support was indicated in
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85656 but never committed. Without
it, the test fails on darwin.
OK to commit?
FX
0001-Testsuite-mark-IPA-test-as-requiring-alias-support.patch
Description: Binary data
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85656
Francois-Xavier Coudert changed:
What|Removed |Added
CC||fxcoudert at gcc dot gnu.org
Hi,
This was a painful one to fix, because I hate regexps, especially when they are
quoted. On darwin, we have this failure:
FAIL: gcc.dg/debug/dwarf2/inline4.c scan-assembler
DW_TAG_inlined_subroutine[^(]*([^)]*)[^(]*(DIE
(0x[0-9a-f]*)
Hi Kito
This issue is due to zcmp and shrink-wrap-separate conflict,
which has been addressed by an under-review patch.
[PATCH 0/2] resolve confilct between RISC-V zcmp and shrink-wrap-separate
https://patchwork.sourceware.org/project/gcc/list/?series=21577
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111081
Francois-Xavier Coudert changed:
What|Removed |Added
Ever confirmed|0 |1
Known to fail|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111081
Bug ID: 111081
Summary: LTO link failure on darwin: g++.dg/lto/pr65276
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component:
Hi,
On darwin (both x86_64-apple-darwin and aarch64-apple-darwin) we see the
following test failure:
FAIL: gcc.dg/lto/20091013-1 c_lto_20091013-1_2.o assemble, -fPIC -r -nostdlib
-O2 -flto
which is due to this extra warning:
In function 'fontcmp',
inlined from 'find_in_cache' at
Hi,
A gentle ping on the revised patch, for Richard or another global reviewer.
Thanks,
FX
> Le 5 août 2023 à 16:20, FX Coudert a écrit :
>
> Hi Richard,
>
> Thanks for your feedback. Here is an amended version of the patch, taking
> into consideration your requests and the following
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111080
--- Comment #2 from sagebar at web dot de ---
@Andrew Pinski
Of course: yes. I did make a mistake there, but only for this case:
> int (*fun_t)(struct foo *); // Leak (even w/o restrict!)
asm:
...
.globl fun_t
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111080
Andrew Pinski changed:
What|Removed |Added
Summary|restrict qualifier causes |[11/12/13/14 Regression]
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111080
--- Comment #1 from Andrew Pinski ---
> static int (*fun_t)(struct foo *); // Leak (even w/o restrict!)
> int (*fun_t)(struct foo *); // Leak (even w/o restrict!)
The above should include the foo debug information as
Hi,
This patch merges the D front-end and run-time library with upstream dmd
26f049fb26, and standard library with phobos 330d6a4fd.
Synchronizing with the latest bug fixes in the v2.105.0-beta.1 release.
D front-end changes:
- Import dmd v2.105.0-beta.1.
- Added predefined
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111080
Bug ID: 111080
Summary: restrict qualifier leaks debug info
Product: gcc
Version: 12.1.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: debug
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110919
--- Comment #3 from Andrew Pinski ---
The first change we get is threadfull1 where there is an extra jump threading.
And then phiopt2 changes:
[local count: 719407024]:
if (l_15(D) != 0)
goto ; [50.00%]
else
goto ; [50.00%]
into:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110918
Andrew Pinski changed:
What|Removed |Added
Last reconfirmed||2023-08-20
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111077
Jonathan Wakely changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |redi at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111036
Andrew Pinski changed:
What|Removed |Added
Depends on||99309
Known to work|
On Thu, 2023-08-17 at 15:20 +0800, Chenghui Pan wrote:
> Seems ARMv8-A only guarantees to preserve low 64-bit value of
> NEON/floating-point register value. I'm not sure that I modify the
> testcase in the right way and maybe we need more investigations. Any
> ideas or suggestion?
Sorry, the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111054
Andrew Pinski changed:
What|Removed |Added
Ever confirmed|0 |1
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111027
Andrew Pinski changed:
What|Removed |Added
Known to fail||4.5.0
Known to work|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111043
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111070
--- Comment #3 from Andrew Pinski ---
In this case name1 and name2 are both ADDR_EXPR rather than SSA_NAMES.
We start with:
```
[local count: 1073741822]:
_1 = (long unsigned int) _ary[0];
_2 = _1 & 7;
if (_2 != 0)
goto ; [34.00%]
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111070
Andrew Pinski changed:
What|Removed |Added
Last reconfirmed||2023-08-20
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110986
--- Comment #20 from Andrew Pinski ---
Only the scalar testcase remains failing now. I will come up with a solution
next week.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111006
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |14.0
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110986
--- Comment #19 from CVS Commits ---
The trunk branch has been updated by Andrew Pinski :
https://gcc.gnu.org/g:70c50c87273d940918225d5c6b03f1ccfb6f978e
commit r14-3337-g70c50c87273d940918225d5c6b03f1ccfb6f978e
Author: Andrew Pinski
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111006
--- Comment #4 from CVS Commits ---
The trunk branch has been updated by Andrew Pinski :
https://gcc.gnu.org/g:70c50c87273d940918225d5c6b03f1ccfb6f978e
commit r14-3337-g70c50c87273d940918225d5c6b03f1ccfb6f978e
Author: Andrew Pinski
Date:
Committed as obvious.
fix misleading identation breaking bootstrap
Fix identation issue introduced by 966f3c13
"Fix format attribute for printf".
gcc/c-family/ChangeLog:
* c-format.cc: Fix identation.
diff --git a/gcc/c-family/c-format.cc
Convert be sinked into a vec_cond if both sides
fold. Unlike other unary operations, we need to check that we still can handle
this vec_cond's first operand is the same as the new truth type.
I tried a few different versions of this patch:
view_convert to the new truth_type but that does not work
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111077
--- Comment #6 from Jonathan Wakely ---
(In reply to Andrew Pinski from comment #5)
> See
> https://gcc.gnu.org/pipermail/libstdc++/2022-October/054899.html
>
> Also
This is just a buggy test.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111063
--- Comment #2 from Andrew Pinski ---
Also I tested GCC 13.2.0 with -fsanitize=float-cast-overflow and GCC does
produce an error message at runtime for the original testcase too.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111063
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
83 matches
Mail list logo
