Hello Harald,
after simplification of constant bound expressions of an explicit
shape spec of an array, we need to ensure that we never obtain
negative extents. In some cases this did happen, and we ICEd
as we hit an assert that this should never happen...
The original testcase by Gerhard exhi
NOTE: A stress test program and a detailed walkthrough that breaks this
patch into manageable parts can be found here:
https://databasearchitects.blogspot.com/2022/06/making-unwinding-through-jit-ed-code.html
The __register_frame/__deregister_frame functions are used to register
unwinding frames f
Hello Harald,
compile time simplification of INDEX(str1,str2,back=.true.) gave wrong
results. Looking at gfc_simplify_index, this appeared to be close to
a complete mess, while the runtime library code - which was developed
later - was a relief.
The solution is to use the runtime library code
This patch is a follow-up improvement to my recent patch for
PR rtl-optimization/7061. That patch added the test case
gcc.target/i386/pr7061-2.c:
float im(float _Complex a) { return __imag__ a; }
For which GCC on x86_64 currently generates:
movq%xmm0, %rax
shrq$32, %rax
This patch addresses PR rtl-optimization/96692 on x86_64, by providing
a define_split for combine to convert the three operation ((A|B)^C)^D
into a two operation sequence using andn when either A or B is the same
register as C or D. This is essentially a reassociation problem that's
only a win if
Hi Jeff,
Sorry for the long delay getting back to this, but after deeper
investigation, it turns out that your tingling spider senses that
the original patch wasn't updating everywhere that was required
were spot on. Although my nvptx testing showed no problems with -O2,
compiling the same tests
Such constants are often subject to the constant synthesis:
int test(int a) {
return a - 31999;
}
test:
movia3, 1
addmi a3, a3, -0x7d00
add a2, a2, a3
ret
This patch optimizes such case as follows:
test:
addia2, a2, 1
We do, of course, mean $host not $target in this case. Corrected thus.
tested on x86_64-darwin and x86_64-linux, pushed to master, thanks
Iain
Signed-off-by: Iain Sandoe
ChangeLog:
* configure: Regenerate.
* configure.ac: Correct use of $host.
---
configure| 4 ++--
confi
If we are building PIC/PIE host executables, and we are building dependent
libs (e.g. GMP) in-tree those libs need to be configured to generate PIC code.
At present, if an --enable-host-shared build is attempted on ELF platforms,
with in-tree dependents, the build will fail with incompatible reloc
Thanks for pushing this.
The patch triggered a (known) regression on
g++.dg/warn/Wstringop-overflow-4.C. In the original submission I
mentioned I would XFAIL it, but forgot to do so. I have pushed the
attached patch.
Note that since this was the last user of EVRP, I think it is now safe
to remo
This patch was motivated by the investigation of Linus Torvalds' spill
heavy cryptography kernels in PR 105930. The di3 expander
handles all rotations by an immediate constant for 1..63 bits with the
exception of 32 bits, which FAILs and is then split by the middle-end.
This patch makes these 32-
On 6/26/2022 9:38 AM, Aldy Hernandez wrote:
Thanks for pushing this.
The patch triggered a (known) regression on
g++.dg/warn/Wstringop-overflow-4.C. In the original submission I
mentioned I would XFAIL it, but forgot to do so. I have pushed the
attached patch.
We both forgot about this :-)
On 6/23/2022 3:21 PM, Dimitar Dimitrov wrote:
If target packs structures by default, the bitfield offset which the
tests validates must be adjusted to not include padding.
Ok for trunk?
gcc/testsuite/ChangeLog:
* gcc.dg/debug/btf/btf-bitfields-1.c: Adjust the checked offsets
On 6/24/2022 9:09 AM, Roger Sayle wrote:
This patch implements the missed optimization described in PR 94026,
where a the shift can be eliminated from the sequence of a shift,
followed by a bit-wise AND followed by an equality/inequality test.
Specifically, ((X << C1) & C2) cmp C3 into (X & (C
On 6/20/2022 11:51 PM, Alexandre Oliva via Gcc-patches wrote:
Systems without preemptive multi-threading require sched_yield calls
to be placed at points in which a context switch might be needed to
enable the test to complete.
Regstrapped on x86_64-linux-gnu, also tested with a cross to
aarc
On Sun, Jun 26, 2022 at 1:12 PM Roger Sayle wrote:
>
>
> This patch is a follow-up improvement to my recent patch for
> PR rtl-optimization/7061. That patch added the test case
> gcc.target/i386/pr7061-2.c:
>
> float im(float _Complex a) { return __imag__ a; }
>
> For which GCC on x86_64 currentl
On Sun, Jun 26, 2022 at 2:04 PM Roger Sayle wrote:
>
>
> This patch addresses PR rtl-optimization/96692 on x86_64, by providing
> a define_split for combine to convert the three operation ((A|B)^C)^D
> into a two operation sequence using andn when either A or B is the same
> register as C or D. T
On Fri, Jun 24, 2022 at 3:26 PM Joseph Myers wrote:
>
> On Fri, 24 Jun 2022, David Malcolm via Gcc-patches wrote:
>
> > > BTW, is this something simple enough I should just commit it without
> > > bugging
> > > the list for approval?
> >
> > The patch seems reasonable to me, but Joseph seems to be
On 2/22/2022 9:40 AM, Andrew MacLeod via Gcc-patches wrote:
This patch simply leverages the existing computation machinery to
re-evaluate values dependent on a newly found non-null value
Ranger associates a monotonically increasing temporal value with every
def as it is defined. When that
On Sun, Jun 26, 2022 at 5:54 PM Roger Sayle wrote:
>
>
> This patch was motivated by the investigation of Linus Torvalds' spill
> heavy cryptography kernels in PR 105930. The di3 expander
> handles all rotations by an immediate constant for 1..63 bits with the
> exception of 32 bits, which FAILs
On 3/24/2022 7:12 AM, Nick Clifton via Gcc-patches wrote:
Hi Guys,
Attached is a proposed patch to fix another Rust demangling bug
reported in PR 105039. I would like to say that this is the
last time that we will see this problem for the Rust demangler,
but I am not that naive...
Hello,
I don’t like the _Float128 vs __float128 business, it’s confusing.
And accordinog to https://gcc.gnu.org/onlinedocs/gcc/Floating-Types.html
they seem to be basically the same thing, so it’s also redundant.
Is there a reason why the standard one, _Float128, can’t be used everywhere?
Mikae
On 5/11/2022 7:48 PM, Alexandre Oliva via Gcc-patches wrote:
There is an assumption in force_edge_cold that, if any edge out of the
same src block has uninitialized probability, then a conditional
branch out of src won't have REG_BR_PROB set.
This assumption is supposed to hold, but buggy gim
On 5/10/2022 12:30 AM, Richard Biener wrote:
On Tue, May 10, 2022 at 12:58 AM Jeff Law via Gcc-patches
wrote:
On 5/5/2022 2:26 AM, Richard Biener via Gcc-patches wrote:
On Thu, May 5, 2022 at 7:04 AM liuhongt wrote:
Optimize
_1 = *srcp_3(D);
_4 = VEC_PERM_EXPR <_1, _1, { 4, 5,
On 5/29/2022 9:53 PM, Vineet Gupta wrote:
These tests validate fp conversions with various rounding modes which
would not work on soft-float ABIs.
On -march=rv64imac/-mabi=lp64 this reduces 5 unique failures (overall 35
due to multi flag combination builds)
gcc/testsuite/Changelog:
*
On 5/30/2022 9:35 PM, Takayuki 'January June' Suwa via Gcc-patches wrote:
Hi all,
In some targets, initialization code for char array may be split into two
parts even if the initialization consists of all zeros:
/* example */
extern void foo(char*);
void test(void) {
char a[256] = { 0, 0,
On 6/16/2022 9:04 AM, Prathamesh Kulkarni via Gcc-patches wrote:
Hi,
I just noticed -fdump-statistics supports asmname sub-option, which
according to the doc states:
"If DECL_ASSEMBLER_NAME has been set for a given decl, use that in the dump
instead of DECL_NAME. Its primary use is ease of use
On 6/21/2022 6:34 PM, Tamar Christina via Gcc-patches wrote:
-Original Message-
From: Tamar Christina
Sent: Tuesday, June 14, 2022 4:58 PM
To: Richard Sandiford ; Richard Biener
Cc: gcc-patches@gcc.gnu.org; nd
Subject: RE: [PATCH 1/2]middle-end Support optimized division by pow2
bitm
I knew you were going to ask for it but was to impatient to propose
those patches to wait anymore.
Attached you'll find what I start to work on. But I am quite
disappointed by the results. At least it's showing that results are not
worst.
To be honest I was also hoping some feedback from po
This patch tweaks the code generated on POWER for integer multiplications
by a constant, by making use of rldimi instructions. Much like x86's
lea instruction, rldimi can be used to implement a shift and add pair
in some circumstances. For rldimi this is when the shifted operand
is known t
On Wed, 2022-06-01 at 11:04 +0200, Aldy Hernandez via Gcc-patches wrote:
> Final patch committed.
>
> All users but one of Value_Range::set_type() have been removed in
> favor of using a constructor taking a type. We still need to delay
> initialization for one use in gimple_infer_range, as it h
Hi Segher!
on 2022/6/25 00:49, Segher Boessenkool wrote:
> Hi!
>
> On Fri, Jun 24, 2022 at 09:03:59AM +0800, Kewen.Lin wrote:
>> on 2022/6/24 03:06, Segher Boessenkool wrote:
>>> On Wed, May 18, 2022 at 10:07:48PM +0800, Kewen.Lin wrote:
As PR103353 shows, we may want to continue to expand a
On Sun, Jun 26, 2022 at 7:53 AM Takayuki 'January June' Suwa
wrote:
>
> Such constants are often subject to the constant synthesis:
>
> int test(int a) {
> return a - 31999;
> }
>
> test:
> movia3, 1
> addmi a3, a3, -0x7d00
> add a2, a2, a3
>
On Mon, 20 Jun 2022 at 12:52, Richard Biener wrote:
>
> On Thu, Jun 16, 2022 at 5:05 PM Prathamesh Kulkarni via Gcc-patches
> wrote:
> >
> > Hi,
> > I just noticed -fdump-statistics supports asmname sub-option, which
> > according to the doc states:
> > "If DECL_ASSEMBLER_NAME has been set for a
> -Original Message-
> From: Richard Sandiford
> Sent: Thursday, June 16, 2022 7:54 PM
> To: Tamar Christina
> Cc: gcc-patches@gcc.gnu.org; nd ; Richard Earnshaw
> ; Marcus Shawcroft
> ; Kyrylo Tkachov
> Subject: Re: [PATCH 1/2]AArch64 Add fallback case using sdot for usdot
>
> Richard
> Am 27.06.2022 um 06:51 schrieb Prathamesh Kulkarni
> :
>
> On Mon, 20 Jun 2022 at 12:52, Richard Biener
> wrote:
>>
>>> On Thu, Jun 16, 2022 at 5:05 PM Prathamesh Kulkarni via Gcc-patches
>>> wrote:
>>>
>>> Hi,
>>> I just noticed -fdump-statistics supports asmname sub-option, which
>>>
On Tue, Jun 21, 2022 at 3:50 AM Uros Bizjak via Gcc-patches
wrote:
>
> On Mon, Jun 20, 2022 at 8:14 PM H.J. Lu wrote:
> >
> > On Tue, May 10, 2022 at 9:25 AM H.J. Lu wrote:
> > >
> > > Mark a function with SYMBOL_FLAG_FUNCTION_ENDBR when inserting ENDBR at
> > > function entry. Skip the 4-byte
On Sat, Jun 25, 2022 at 11:09 AM Tom de Vries via Gcc-patches
wrote:
>
> Hi,
>
> When building gdbserver with -fsanitize=thread (added to CFLAGS/CXXFLAGS) we
> run into:
> ...
> ld: ../libiberty/libiberty.a(safe-ctype.o): warning: relocation against \
> `__tsan_init' in read-only section `.text'
egrep and fgrep have been deprecated for a long time, and the next grep
release will emit a warning if egrep or fgrep is invoked:
https://git.savannah.gnu.org/cgit/grep.git/commit/?id=a951562
To prevent us from a lot of these warnings in the future, we should stop
using egrep and fgrep. These pa
egrep has been deprecated in favor of grep -E for a long time, and the
next GNU grep release (3.8 or 4.0) will print a warning if egrep is used.
Unfortunately, old hosts with non-GNU grep may lack the support for -E
option. Use AC_PROG_EGREP and $EGREP variable so we'll work fine on
both old and n
egrep/fgrep has been deprecated in favor of grep -E/-F for a long time,
and the next grep release (3.8 or 4.0) will print a warning if egrep or
fgrep is used. Stop using egrep and fgrep so we won't see the warning.
But, we can't simply replace egrep to grep -E or fgrep to grep -F or the
build wil
fgrep has been deprecated in favor of grep -F for a long time, and the
next grep release (3.8 or 4.0) will print a warning of fgrep is used.
But, we can't simply replace fgrep to grep -F, or the build will break
with some non-GNU grep implementations (lacking -F support).
As "add-gnu-debuglink" is
egrep has been deprecated in favor of grep -E for a long time, and the
next grep release (3.8 or 4.0) will print a warning of egrep is used.
Stop using egrep so we won't see the warning.
However, simply replacing egrep with grep -E will break build on some
systems (notably Solaris) w/o a POSIX-con
egrep has been deprecated in favor of grep -E for a long time, and the
next grep release (3.8 or 4.0) will print a warning of egrep is used.
Stop using egrep so we won't see the warning.
Some non-POSIX grep implementations does not support -E option, so for
test_summary and warn_summary we prefer
Python 2 has been EOL'ed for two years. egrep has been deprecated
for many years and the next grep release will start to print warning if
it is used.
-E option may be unsupported by some non-POSIX grep implementations, but
gcc-auto-profile won't work on non-Linux systems anyway.
contrib/ChangeLo
On Mon, Jun 27, 2022 at 7:25 AM Tamar Christina via Gcc-patches
wrote:
>
> > -Original Message-
> > From: Richard Sandiford
> > Sent: Thursday, June 16, 2022 7:54 PM
> > To: Tamar Christina
> > Cc: gcc-patches@gcc.gnu.org; nd ; Richard Earnshaw
> > ; Marcus Shawcroft
> > ; Kyrylo Tkachov
fgrep has been deprecated in favor of grep -F for a long time, and the
next grep release (3.8 or 4.0) will print a warning of fgrep is used.
Stop using fgrep so we won't see the warning.
We can't hard code grep -F here or it may break build on hosts w/o GNU
grep. autoconf documentation contains a
Cherry-pick libffi commit 280fe78d37f58927b280e2e316a2ae19201f2b83,
and regenerate configure.
libffi/ChangeLog:
* configure.ac: Call AC_PROG_EGREP, and use $EGREP instead of
egrep.
* configure: Regenerate.
---
libffi/configure| 270 ++--
> egrep has been deprecated in favor of grep -E for a long time, and the
> next grep release (3.8 or 4.0) will print a warning of egrep is used.
> Stop using egrep so we won't see the warning.
>
> However, simply replacing egrep with grep -E will break build on some
> systems (notably Solaris) w/o
49 matches
Mail list logo
