Hi!
The following patch adds support for bitfields to push_partial_def.
Previously pd.offset and pd.size were counted in bytes and maxsizei
in bits, now everything is counted in bits.
Not really sure how much of the further code can be outlined and moved, e.g.
the full def and partial def code d
It is a good solution.
Thanks,
Feng
From: Martin Jambor
Sent: Saturday, February 22, 2020 2:15 AM
To: Feng Xue OS; Tamar Christina; Jan Hubicka; gcc-patches@gcc.gnu.org
Cc: nd
Subject: Re: [PATCH] Fix bug in recursiveness check for function to be cloned
(
On 2/11/20 7:46 AM, Roman Zhuykov wrote:
[snip]
Since I have to ask again about backports, I've decided to make few more
steps and with Alexander's help created new patch which rewords the
whole option description and covers items (3), (4) and (8). CCing Jakub
and Richard as release managers, al
On 2/17/20 10:54 AM, Jason Merrill wrote:
On 2/14/20 9:06 PM, Martin Sebor wrote:
On 2/13/20 3:59 PM, Jason Merrill wrote:
On 2/12/20 9:21 PM, Martin Sebor wrote:
On 2/11/20 5:28 PM, Jason Merrill wrote:
On 2/11/20 9:00 PM, Martin Sebor wrote:
r270155, committed in GCC 9, introduced a transf
The attached patch fixes a problem noted in the libffi testsuite. This is a
particular problem
on 32-bit hppa*-hpux*.
We pass homogeneous SFmode and DFmode aggregates in the general registers
instead of the floating
point registers that are used to pass SFmode and DFmode values.
ASM_DECLARE_F
On Thu, Feb 20, 2020 at 12:28:42AM +, Jason Merrill wrote:
> On 2/19/20 7:30 PM, Marek Polacek wrote:
> > On Fri, Feb 14, 2020 at 09:12:58AM +0100, Jason Merrill wrote:
> > > On 2/13/20 8:56 PM, Marek Polacek wrote:
> > > > My P0388R4 patch changed build_array_conv to create an identity
> > > >
> > Sounds good. I'll get those setup and running and will report back on
> > findings. What's the preferred way to measure codesize? I'm assuming
> > by default the code pages are aligned so smaller differences would need to
> > trip
> over the boundary to actually show up.
>
> You can use the s
On Fri, Feb 21, 2020 at 1:04 AM Kito Cheng wrote:
> * config/riscv/riscv.c (riscv_emit_float_compare): Change the code gen
> for LTGT.
> (riscv_rtx_costs): Update cost model for LTGT.
Thanks. This looks good to me.
Jim
On Fri, 21 Feb 2020, Patrick Palka wrote:
> This patch adds std::shift_left and std::shift_right. Alhough these are
> STL-style algos, they are nonetheless placed in because
> they make use of some functions in the ranges namespace that are more easily
> reachable from than from , namely
> rang
On Wed, 2020-02-19 at 11:02 +0100, Uros Bizjak wrote:
> Default testsuite flags do not enable V8QI (MMX) vector mode for
> 32bit x86 targets. Require vect_multiple_sizes effective target in
> scan-tree-dump to avoid "LOOP EPILOGUE VECTORIZED" failure.
>
> Tested on x86_64-linux-gnu {,-m32}.
>
>
On Wed, 2020-02-19 at 12:59 +, Richard Sandiford wrote:
> This PR is about a case in which the clobbers at the start of
> an EH receiver can lead to registers becoming unnecessarily
> live in predecessor blocks. My first attempt at fixing this
> made sure that we update the bb liveness info ba
On Thu, 2020-02-20 at 22:17 -0300, Alexandre Oliva wrote:
> mkheaders.in uses substitutions of @SHELL@ to run fixinc.sh and
> mkinstalldirs. Problem is, SHELL comes from CONFIG_SHELL for the
> build system, and it needs not match whatever is available at an
> unrelated host system after installati
On Fri, 2020-02-21 at 18:59 +0100, Martin Jambor wrote:
> Hi,
>
> On Tue, Feb 18 2020, Feng Xue OS wrote:
> > Currently, for self-recursive call, we never use value originated from
> > non-passthrough
> > jump function as source to avoid propagation explosion, but self-dependent
> > value is
> >
The quotes should surround all of the literal content from the pragma
that has incorrect usage.
Fixed as below,
tested on x86_64-apple-darwin16,
applied to master,
thanks
Iain
2020-02-21 Iain Sandoe
PR target/93860
* config/darwin-c.c (pop_field_alignment): Adjust quoting of
On 21/02/20 12:38, Tobias Burnus wrote:
Hmm, that sounds like papering over a real bug.
It is possible, I tried using DECL_INITIAL to nullify cfi.n but it did
not made any difference.
I tried to play with optimization and up to -O1 it does not seem to
crash but it always seems to crash at
This patch adds std::shift_left and std::shift_right. Alhough these are
STL-style algos, they are nonetheless placed in because
they make use of some functions in the ranges namespace that are more easily
reachable from than from , namely
ranges::next and ranges::swap_ranges.
This implementatio
On Fri, Feb 21, 2020 at 02:14:26PM -0500, Marek Polacek wrote:
> This was approved in the Prague 2020 WG21 meeting so let's adjust the
> comment. Since it's supposed to be a DR I think we should no longer
> limit it to C++20.
Which is what clang++ trunk does.
Marek
This was approved in the Prague 2020 WG21 meeting so let's adjust the
comment. Since it's supposed to be a DR I think we should no longer
limit it to C++20.
Bootstrapped/regtested on x86_64-linux, ok for trunk?
2020-02-21 Marek Polacek
P1957R2
* typeck2.c (check_narrowing): C
Hi,
On Thu, Feb 20 2020, Feng Xue OS wrote:
> This is a simpel and nice fix, but could suppress some CP opportunities for
> self-recursive call. Using the test case as example, the first should be a
> for-all-context clone, and the call "recur_fn (i, 1, depth + 1)" is replaced
> with
> a newly c
This is a crash in cp_parser_check_class_key:
tree type_decl = TYPE_MAIN_DECL (type);
tree name = DECL_NAME (type_decl); // HERE
because TYPE_MAIN_DECL of type was null as it's not a class type.
Instead of checking CLASS_TYPE_P we should simply check class_key
a bit earlier (in this case it was
Hi,
On Tue, Feb 18 2020, Feng Xue OS wrote:
> Currently, for self-recursive call, we never use value originated from
> non-passthrough
> jump function as source to avoid propagation explosion, but self-dependent
> value is
> missed. This patch is made to fix the bug.
>
> Bootstrapped/regtested o
We merged support for -std=c++20 to trunk, so -std=c++2a is only
needed in GCC 9 and earlier.
---
htdocs/projects/cxx-status.html | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/htdocs/projects/cxx-status.html b/htdocs/projects/cxx-status.html
index 1b54ea97..47278613 100644
I'm assuming the new papers have not been implemented yet.
(P1957R1 is implemented though, I'll update the page separately.)
Pushed.
---
htdocs/projects/cxx-status.html | 161 +---
1 file changed, 126 insertions(+), 35 deletions(-)
diff --git a/htdocs/projects/cxx-sta
Another piece of P1614R2.
* include/std/optional (operator<=>(optional, optional))
(operator<=>(optional, nullopt), operator<=>(optional, U)):
Define for C++20.
* include/std/tuple (__tuple_cmp): New helper function for <=>.
(operator<=>(tuple, tuple...)): D
Ping: https://gcc.gnu.org/ml/gcc-patches/2020-02/msg00883.html
On 2/14/20 3:41 PM, Martin Sebor wrote:
Because attribute weakref introduces a kind of a definition, it can
only be applied to declarations of symbols that are not defined. GCC
normally issues a warning when the attribute is applied
Hi,
this fixes the signal handler calling signal unsafe vfprintf and/or passing
uninitialized memory to unlink in signal handler.
This time it is the patch for the gcc-9 branch.
The difference to the gcc-8 branch is in tool_cleanup:
The variable that suppress the vfprintf is verbose = false;
not
Hi Roman,
On 2/21/20 3:49 PM, Roman Zhuykov wrote:
11.02.2020 14:00, Richard Earnshaw (lists) wrote:
+(define_insn "*doloop_end"
+ [(parallel [(set (pc)
+ (if_then_else
+ (ne (reg:SI LR_REGNUM) (const_int 1))
+ (label_ref (match_opera
11.02.2020 14:00, Richard Earnshaw (lists) wrote:
> +(define_insn "*doloop_end"
> + [(parallel [(set (pc)
> + (if_then_else
> + (ne (reg:SI LR_REGNUM) (const_int 1))
> + (label_ref (match_operand 0 "" ""))
> + (pc)))
>
Hi Kyrill,
On 21/02/2020 11:47, Kyrill Tkachov wrote:
Hi Dennis,
On 2/11/20 12:03 PM, Dennis Zhang wrote:
Hi all,
On 16/12/2019 13:45, Dennis Zhang wrote:
> Hi all,
>
> This patch is part of a series adding support for Armv8.6-A features.
> It depends on the Arm Armv8.6-A CLI patch,
> https:/
Andrea Corallo writes:
> With this patch the first insn of the low loop overhead 'doloop_begin'
> is expanded by 'doloop_modify' in loop-doloop.c. The same does not
> happen with SMS.
That certainly works correct as in your first patch, doloop_begin
pattern also have "!flag_modulo_sched" conditi
Hi Andrea,
On 2/19/20 1:01 PM, Andrea Corallo wrote:
Hi all,
Second version of the patch here addressing comments.
This patch enables the Armv8.1-M Mainline LOB (low overhead branch)
extension
low overhead loops (LOL) feature by using the 'loop-doloop' pass.
Given the following function:
v
This testcase is susceptible to memory location details and start to fail
with default to -fno-common. Use -fcommon to set expected testing conditions.
Tested on x86_64-linux-gnu {,-m32}.
2020-02-21 Uroš Bizjak
* gcc.target/i386/pr69052.c: Require target ia32.
(dg-options): Add -fcom
Hi Kyrill,
The arm_bf16.h is only used for scalar operations. That is how the
aarch64 versions are implemented too.
Thanks,
Delia
On 2/21/20 2:06 PM, Kyrill Tkachov wrote:
Hi Delia,
On 2/19/20 5:25 PM, Delia Burduv wrote:
Hi,
Here is the latest version of the patch. It just has some minor
Hi,
The commit r10-6721-g8d1a1cb1b816381bf60cb1211c93b8eba1fe1472 has changed
the name of the type that is used for the return value of the Fortran
acc_get_property function without adapting the test acc_get_property.f90.
This obvious patch fixes that problem. Committed as
r10-6782-g83d45e1d7155a
When I forward ported the scatter/gather patterns from my GCC 9
implementation I didn't notice that GCC 10 has a different naming
scheme. :-(
The patterns were being used because all GCN vector loads end up being
scatter/gather, but not by the actual vectorizer. The test fails were
there to s
Hi Delia,
On 2/19/20 5:25 PM, Delia Burduv wrote:
Hi,
Here is the latest version of the patch. It just has some minor
formatting changes that were brought up by Richard Sandiford in the
AArch64 patches
Thanks,
Delia
On 1/22/20 5:29 PM, Delia Burduv wrote:
> Ping.
>
> I will change the tests t
On 2/21/20 1:56 PM, José Rui Faustino de Sousa wrote:
Since the cfi.n pointer is uninitialized in some infrequent situations
(using -static-libgfortran seems to do the trick) the pointer seems to
contain garbage and a segmentation fault is generated
Hmm, that sounds like papering over a real b
Hi all!
Proposed patch to solve problems with memory handling with allocatable
intent(out) arrays with bind(c).
The patch also seems to affect PR92189.
Patch tested only on x86_64-pc-linux-gnu.
The code currently generated tries to deallocate the artificial cfi.n
pointer before it is associ
On 18/02/2020 15:30, Jonathan Wakely wrote:
On 18/02/20 14:48 +0100, Sebastian Huber wrote:
Hello,
On 18/02/2020 07:46, Thomas Rodgers wrote:
This patch adds the c++2a semaphore header and binary_semaphore type.
The implementation is not complete, this patch is just to solicit
initial feedbac
On Fri, 21 Feb 2020, Martin Jambor wrote:
> Hi,
>
> the testcase is another example - in addition to recent PR 93516 - where
> the SRA access verifier is confused by the fact that get_ref_base_extent
> can return different sizes for the same type, depending whether they are
> COMPONENT_REF or not
On 2/21/20 11:51 AM, Kyrill Tkachov wrote:
Hi Mihail,
On 2/19/20 4:27 PM, Mihail Ionescu wrote:
Hi Christophe,
On 01/23/2020 09:34 AM, Christophe Lyon wrote:
> On Mon, 20 Jan 2020 at 19:01, Mihail Ionescu
> wrote:
>>
>> Hi,
>>
>> This patch fixes the scalar shifts tests added in:
>> https:/
This patch fixes any obvious typo in the definition of vec_seriesv64di.
It's never worked, so the fact it's taken this long for me to notice
shows how little the middle-end takes advantage of this pattern. :-(
Andrew
amdgcn: fix mode in vec_series
2020-02-20 Andrew Stubbs
gcc/
* config
This patch changes the way VGPR register pairs (for 64-bit values) are
allocated.
There are no hardware restrictions on the alignment of such pairs
(unlike for scalar registers), but there's also not a full set of 64-bit
instructions, meaning that many operations get decomposed into two or
mo
Hi,
the testcase is another example - in addition to recent PR 93516 - where
the SRA access verifier is confused by the fact that get_ref_base_extent
can return different sizes for the same type, depending whether they are
COMPONENT_REF or not. In the previous bug I decided to keep the
verifier c
Hi Mihail,
On 2/19/20 4:27 PM, Mihail Ionescu wrote:
Hi Christophe,
On 01/23/2020 09:34 AM, Christophe Lyon wrote:
> On Mon, 20 Jan 2020 at 19:01, Mihail Ionescu
> wrote:
>>
>> Hi,
>>
>> This patch fixes the scalar shifts tests added in:
>> https://gcc.gnu.org/ml/gcc-patches/2019-11/msg01195.h
Hi Dennis,
On 2/11/20 12:03 PM, Dennis Zhang wrote:
Hi all,
On 16/12/2019 13:45, Dennis Zhang wrote:
> Hi all,
>
> This patch is part of a series adding support for Armv8.6-A features.
> It depends on the Arm Armv8.6-A CLI patch,
> https://gcc.gnu.org/ml/gcc-patches/2019-11/msg02195.html.
> It
Hi Delia,
On 2/19/20 5:23 PM, Delia Burduv wrote:
Hi,
Here is the latest version of the patch. It just has some minor
formatting changes that were brought up by Richard Sandiford in the
AArch64 patches
Thanks,
Delia
On 1/31/20 3:23 PM, Delia Burduv wrote:
Here is the updated patch. The cha
SVE was missing support for -mlow-precision-sqrt, which meant that
-march=armv8.2-a+sve -mlow-precision-sqrt could cause a performance
regression compared to -march=armv8.2-a -mlow-precision-sqrt.
Tested on aarch64-linux-gnu and aarch64_be-elf, pushed.
Richard
2020-02-21 Richard Sandiford
g
SVE was missing support for -mlow-precision-div, which meant that
-march=armv8.2-a+sve -mlow-precision-div could cause a performance
regression compared to -march=armv8.2-a -mlow-precision-div.
I ended up doing this much later than originally intended, sorry...
Tested on aarch64-linux-gnu and aar
Committed to wwwdocs git.
commit 578a32e2f9215ccf96bd580d275fa12c22aa45a5
Author: Jonathan Wakely
Date: Fri Feb 21 10:27:39 2020 +
Document more libstdc++ changes
diff --git a/htdocs/gcc-10/changes.html b/htdocs/gcc-10/changes.html
index 5a959a10..2920714a 100644
--- a/htdocs/gcc-10/
We now have more than 32 scalar and vector float modes, so the
32-bit AARCH64_APPROX_MODE would invoke UB for some of them.
Bumping to a 64-bit mask fixes that... for now.
Ideally we'd have a static assert to trap this, but logically
it would go at file scope. I think it would be better to wait
u
The rsqrt path of aarch64_emit_approx_sqrt created a pseudo
register that it never used.
Tested on aarch64-linux-gnu and aarch64_be-elf, pushed.
Richard
2020-02-21 Richard Sandiford
gcc/
* config/aarch64/aarch64.c (aarch64_emit_approx_sqrt): Don't create
an unused xmsk regis
The fix for PR80530 included an accidental flipping of the
flag_finite_math_only check, so that -ffinite-math-only (and thus
-ffast-math) disabled approximate sqrt rather than enabling it.
This is tested by later patches but seemed worth splitting out.
Tested on aarch64-linux-gnu and aarch64_be-e
This applies file mapping when emitting the directory table
directly instead of using the assemblers .file directive where
we already correctly apply the map. Notably the non-assembler
path is used for the early debug emission for LTO.
Bootstrapped and tested on x86_64-unknown-linux-gnu.
OK for
On Thu, Feb 20, 2020 at 6:33 PM Peter Bergner wrote:
>
> On 2/20/20 1:47 AM, Segher Boessenkool wrote:
> > On Wed, Feb 19, 2020 at 09:17:26PM -0600, Peter Bergner wrote:
> >> This passed bootstrap and regtesting on powerpc64le-linux and
> >> powerpc64-linux
> >> (in both 32-bit and 64-bit modes)
On Thu, 20 Feb 2020, Jan Hubicka wrote:
> > This fixes bogus path-based disambiguation of mismatched array shape
> > accesses.
> >
> > Bootstrap & regtest running on x86_64-unknown-linux-gnu.
> >
> > Honza, is this the correct place to detect this or were we not
> > supposed to arrive there?
> >
Hello,
ping for patch https://gcc.gnu.org/ml/gcc-patches/2020-02/msg00554.html.
Thanks,
Paul.
On 2/10/20 19:22, Paul Gofman wrote:
> ChangeLog:
> PR target/91489
> * config/i386/i386.md (simple_return): Also check
> for ms_hook_prologue function attribute.
> * config/
- Using gcc.dg/torture/pr91323.c as testcase, so no new testcase
introduced.
- We use 3 eq compare for LTGT compare before, in order to prevent exception
flags setting when any input is NaN.
- According latest GCC document LTGT and discussion on pr91323
LTGT should signals on NaNs, li
58 matches
Mail list logo
