Hello All,
I am badly stuck at custom float encode and decode, I humbly request your
assistance.
I am trying to incorporate in custom floats in RISCV-32 elf, I am encoding
and assigning to image at line 2985 in
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102943
--- Comment #19 from hubicka at kam dot mff.cuni.cz ---
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102943
>
> Aldy Hernandez changed:
>
>What|Removed |Added
>
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102943
>
> Aldy Hernandez changed:
>
>What|Removed |Added
>
> Depends on||103058
>
> --- Comment
Hi,
On Wed, Nov 03 2021, Richard Biener wrote:
> On Mon, 1 Nov 2021, Martin Jambor wrote:
>
>> Hello,
>>
>> I'd like to ping this patch.
>>
>> Thanks,
>>
>> Martin
>>
>>
>> On Wed, Oct 13 2021, Martin Jambor wrote:
>> > Hi,
>> >
>> > in spring I added code eliminating any statements using
> On Thu, Nov 04, 2021 at 05:13:41PM +0100, Jan Hubicka via Gcc-patches wrote:
> > this patch workarounds ICE in gimple_static_chain_flags. I added a
> > sanity check that the nested function is never considered interposable
> > because such situation makes no sense: nested functions have no
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103082
Jan Hubicka changed:
What|Removed |Added
Ever confirmed|0 |1
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102967
--- Comment #6 from Andreas Schwab ---
&*E is allowed for E == NULL, but I don't think this can be generalized to
>m.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102961
--- Comment #3 from John Parke ---
I think the problem is caused by:
>> 0711-738 ERROR: Input file /usr/gcc-11.2.0-build/./gcc/ppc64/crtcxa_s.o:
See below:
XCOFF32 object files are not allowed in 64-bit mode.
# @multilib_flags@ is
On Thu, Nov 04, 2021 at 05:13:41PM +0100, Jan Hubicka via Gcc-patches wrote:
> this patch workarounds ICE in gimple_static_chain_flags. I added a
> sanity check that the nested function is never considered interposable
> because such situation makes no sense: nested functions have no static
> API
> On 11/4/21 15:12, Jan Hubicka via Gcc-patches wrote:
> > |Bootstrapped/regtested x86_64-linux, plan to commit after bit more
> > testing.|
>
> Can you please install the patch after the current MOD REF crashes are fixed?
> It will help us with the future bisection.
Sure, this is what I am
Hi,
this patch workarounds ICE in gimple_static_chain_flags. I added a
sanity check that the nested function is never considered interposable
because such situation makes no sense: nested functions have no static
API and can not be safely merged across translation units.
It turns out however that
On 11/4/21 15:12, Jan Hubicka via Gcc-patches wrote:
|Bootstrapped/regtested x86_64-linux, plan to commit after bit more testing.|
Can you please install the patch after the current MOD REF crashes are fixed?
It will help us with the future bisection.
Thanks,
Martin
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103058
--- Comment #5 from CVS Commits ---
The master branch has been updated by Jan Hubicka :
https://gcc.gnu.org/g:d3f7a2fa64f8777cb7eae1b99ff80fbe717095ac
commit r12-4914-gd3f7a2fa64f8777cb7eae1b99ff80fbe717095ac
Author: Jan Hubicka
Date: Thu
It's been inconvenient that pretty-printing of PTRMEM_CST didn't display
what member the constant refers to.
Adding that is complicated by the absence of a langhook for CONSTANT_CLASS_P
nodes; the simplest fix for that is to use the tcc_exceptional hook for
tcc_constant as well.
Tested
* Martin Sebor:
> Thanks for the reminder. I have not forgotten about this.
> I agreed in our discussion and in the GCC bug report where this
> came up (PR 101751) that the GCC logic here is wrong and should
> be relaxed. I consider it a GCC bug so I plan to make the change
> in the bug fixing
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102967
--- Comment #5 from jbeulich at suse dot com ---
(In reply to Martin Sebor from comment #4)
> The expression pa->c is only valid if pa points to a valid object.
Well, yes, you may not deref pa if it's NULL, i.e. I agree for pa->c. But is
>c
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102967
--- Comment #4 from Martin Sebor ---
The expression pa->c is only valid if pa points to a valid object.
On Thu, Nov 04, 2021 at 12:13:51PM +0100, Richard Biener wrote:
> As a general comment I wonder whether doing this fully in the C++
> frontend leveraging the constexpr support is a better approach, esp.
> before we end up putting all initializers into a single function ...
> even partly constexpr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103058
--- Comment #4 from hubicka at kam dot mff.cuni.cz ---
Hi,
I am testing the following to unbreak fortran.
However the real bug is that binds_to_current_def should work on whole
WPA and be independent of partitioning. I remember I had patch
On 11/4/21 1:03 AM, Florian Weimer via Libc-alpha wrote:
This code:
#include
#include
void
f (pthread_key_t key)
{
pthread_setspecific (key, MAP_FAILED);
}
Results in a warning:
t.c: In function ‘f’:
t.c:7:3: warning: ‘pthread_setspecific’ expecting 1 byte in a region of size 0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103083
Martin Jambor changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |jamborm at gcc dot
gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103083
Martin Liška changed:
What|Removed |Added
Summary|Wrong code due to ipa-cp's |[10/11/12 Regression] Wrong
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102943
Aldy Hernandez changed:
What|Removed |Added
Depends on||103058
--- Comment #18 from Aldy
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103083
Bug ID: 103083
Summary: Wrong code due to ipa-cp's value range propagation
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103081
--- Comment #4 from M Welinder ---
That version of clang does not do "using enum" at all. clang 13 accepts this
code, but it has other issues with "using enum".
On 11/4/21 14:09, Richard Biener wrote:
But we shouldn't start with the current global options but with ones
we saved for
optimize attribute/pragma processing, no?
We hit the issue when we combine cmdline and pragma optimize options.
Problem of -gtoggle is that it does not directly
On Thu, Nov 04, 2021 at 12:19:34PM +, Tamar Christina wrote:
> I'm not sure the precision matters since if the conversion resulted in not
> enough
> precision such that It influences the compare it would have been optimized
> out.
You can't really rely on other optimizations being
On 11/3/2021 2:15 AM, Richard Biener via Gcc-patches wrote:
On Tue, Nov 2, 2021 at 4:53 PM Jeff Law wrote:
I was wandering spec chasing down instances where we should be
generating bit-test, bit-set and bit-clear types of instructions for our
target when I ran across a generic missed
Could you add the information about zdinx implied zfinx to riscv_implied_info_t?
Thanks!
On Thu, Oct 28, 2021 at 9:56 PM jiawei wrote:
>
> Co-Authored-By: sinan
> ---
> gcc/common/config/riscv/riscv-common.c | 6 ++
> gcc/config/riscv/riscv-opts.h | 6 ++
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103080
--- Comment #3 from Iain Sandoe ---
(In reply to hubicka from comment #1)
> The cdtor merging code is predating LTO - it is also used for collect2
> path on targets w/o cdtor sections.
Even so, I do not see how it can work there either*** -
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101715
--- Comment #12 from Marek Polacek ---
OK, I'd totally forgotten about this PR.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103082
Martin Liška changed:
What|Removed |Added
Known to fail||12.0
Target Milestone|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103082
Bug ID: 103082
Summary: [12 Regression] gcc/poly-int.h:1162:5: runtime error:
left shift of negative value -40
Product: gcc
Version: 12.0
Status: UNCONFIRMED
On Thu, Oct 28, 2021 at 9:57 PM jiawei wrote:
>
> Co-Authored-By: sinan
> ---
> gcc/config/riscv/arch-canonicalize | 1 +
> gcc/config/riscv/constraints.md| 3 ++-
> gcc/config/riscv/riscv.c | 15 +--
> 3 files changed, 16 insertions(+), 3 deletions(-)
>
> diff --git
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103081
--- Comment #3 from Richard Biener ---
Confirmed on the GCC 11 branch head and trunk. clang complains:
> clang++-11 -S t.C -std=c++20
t.C:4:9: error: expected unqualified-id
using enum Pig;
^
t.C:10:18: error: no member named 'OINK'
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103081
--- Comment #2 from Marek Polacek ---
Started with r11-5003.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103080
--- Comment #2 from Richard Biener ---
IIRC there is also an older bug about CTOR/DTOR order across multiple TUs where
with -flto be behave differently than without where I said it might be nice to
preserve linker command line order (we have
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103081
Marek Polacek changed:
What|Removed |Added
Ever confirmed|0 |1
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103072
--- Comment #3 from Jeremy R. ---
(In reply to Jakub Jelinek from comment #1)
> So maybe the switchconv pass could be
> improved not to do just the linear etc. expression handling, but also
> consider code sequences that are the same except for
Check leal and addl for x32 to fix:
FAIL: gcc.target/i386/amxtile-3.c scan-assembler addq[ \\t]+\\$12
FAIL: gcc.target/i386/amxtile-3.c scan-assembler leaq[ \\t]+4
FAIL: gcc.target/i386/amxtile-3.c scan-assembler leaq[ \\t]+8
* gcc.target/i386/amxtile-3.c: Check leal/addl for x32.
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102943
--- Comment #17 from CVS Commits ---
The master branch has been updated by Aldy Hernandez :
https://gcc.gnu.org/g:6a9678f0b30d36ae13259ad635e175a1e24917a1
commit r12-4905-g6a9678f0b30d36ae13259ad635e175a1e24917a1
Author: Aldy Hernandez
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102943
--- Comment #16 from CVS Commits ---
The master branch has been updated by Aldy Hernandez :
https://gcc.gnu.org/g:e4411622690654cdc530c6262c7115a9e15dc359
commit r12-4904-ge4411622690654cdc530c6262c7115a9e15dc359
Author: Aldy Hernandez
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102943
--- Comment #15 from CVS Commits ---
The master branch has been updated by Aldy Hernandez :
https://gcc.gnu.org/g:5ea1ce43b6070aaa94882e8b15f3340344aaa6b2
commit r12-4903-g5ea1ce43b6070aaa94882e8b15f3340344aaa6b2
Author: Aldy Hernandez
Date:
The range_of_expr method provides better caching than range_on_edge.
If we have a statement, we can just it and avoid the range_on_edge
dance. Plus we can use all the range_of_expr fanciness.
Tested on x86-64 and ppc64le Linux with the usual regstrap. I also
verified that the before and after
We are currently calculating implicit PHI relations for all PHI
arguments. This creates unecessary work, as we only care about SSA
names in the import bitmap. Similarly for inter-path relationals. We
can avoid things not in the bitmap.
Tested on x86-64 and ppc64le Linux with the usual
We already attempt to resolve the current path on entry to
find_paths_to_name(), so there's no need to do so again for each
exported range since nothing has changed.
Removing this redundant calculation avoids 22% of calls into the path
solver.
Tested on x86-64 and ppc64le Linux with the usual
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103081
Bug ID: 103081
Summary: [ICE] with "using enum"
Product: gcc
Version: 11.1.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103080
--- Comment #1 from hubicka at kam dot mff.cuni.cz ---
The cdtor merging code is predating LTO - it is also used for collect2
path on targets w/o cdtor sections.
I guess the DECL_UID compare is not very safe things to do since it
depends on the
ping
From: Wilco Dijkstra
Sent: 02 June 2021 11:21
To: GCC Patches
Cc: Kyrylo Tkachov ; Richard Sandiford
Subject: [PATCH] AArch64: Improve address rematerialization costs
Hi,
Given the large improvements from better register allocation of GOT accesses,
I decided to generalize it to get
v2: rebased
The --with-cpu/--with-arch configure option processing not only checks valid
arguments
but also sets TARGET_CPU_DEFAULT with a CPU and extension bitmask. This isn't
used
however since a --with-cpu is translated into a -mcpu option which is processed
as if
written on the
On Wed, Oct 20, 2021 at 5:43 AM H.J. Lu wrote:
>
> When --enable-cet is used to configure GCC, enable Intel CET in libffi.
>
> * Makefile.am (AM_CFLAGS): Add $(CET_FLAGS).
> (AM_CCASFLAGS): Likewise.
> * configure.ac (CET_FLAGS): Add GCC_CET_FLAGS and AC_SUBST.
> *
Hi,
this patch implements the (long promised) intraprocedural dataflow for
propagating eaf flags, so we can handle parameters that participate
in loops in SSA graphs. Typical example are acessors that walk linked
lists, for example.
I implemented dataflow using the standard iteration over BBs in
Hi!
For -fstrong-eval-order (default for C++17 and later) we make sure to
gimplify arguments in the right order, but as the following testcase
shows that is not enough.
The problem is that some lvalues can satisfy the is_gimple_val / fb_rvalue
predicate used by gimplify_arg for is_gimple_reg_type
Pushed.
Doing so, one can see:
$ git gcc-verify a50914d2111c72d2cd5cb8cf474133f4f85a25f6 -v
Checking a50914d2111c72d2cd5cb8cf474133f4f85a25f6: FAILED
ERR: unchanged file mentioned in a ChangeLog: "gcc/common.opt"
ERR: unchanged file mentioned in a ChangeLog (did you mean
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103042
Tamar Christina changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
On Thu, 4 Nov 2021 at 12:42, Richard Biener via Gcc wrote:
>
> On Thu, Nov 4, 2021 at 12:57 PM Segher Boessenkool
> wrote:
> >
> > On Fri, Oct 29, 2021 at 09:32:21AM +0200, Richard Biener via Gcc-patches
> > wrote:
> > > On Fri, Oct 29, 2021 at 2:42 AM Bernhard Reutner-Fischer via
> > >
On Thu, 4 Nov 2021 at 12:42, Richard Biener via Gcc wrote:
>
> On Thu, Nov 4, 2021 at 12:57 PM Segher Boessenkool
> wrote:
> >
> > On Fri, Oct 29, 2021 at 09:32:21AM +0200, Richard Biener via Gcc-patches
> > wrote:
> > > On Fri, Oct 29, 2021 at 2:42 AM Bernhard Reutner-Fischer via
> > >
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103080
Bug ID: 103080
Summary: LTO alters the ordering of static
constructors/destructors in pass_ipa_cdtor_merge.
Product: gcc
Version: 12.0
Status: UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103042
--- Comment #3 from CVS Commits ---
The master branch has been updated by Tamar Christina :
https://gcc.gnu.org/g:5914a7b5c637c9007283226f200dcab8b745abc8
commit r12-4900-g5914a7b5c637c9007283226f200dcab8b745abc8
Author: Tamar Christina
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103079
--- Comment #10 from Andrew Macleod ---
That patch wont generally work until rangeops op1_range routines are adjusted
to deal with undefined being passed in.. I think it assumes until now that its
been trimmed out.
(In reply to Richard Biener
On Thu, 4 Nov 2021, Tamar Christina wrote:
> Hi All,
>
> This test hopefully fixes all the remaining target specific test issues by
>
> 1: Unrolling all add testcases by 16 using pragma GCC unroll
> 2. On armhf use Adv.SIMD instead of MVE to test. MVE's autovec is too
> incomplete
>to be a
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103079
--- Comment #9 from Andrew Macleod ---
Created attachment 51735
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=51735=edit
patch for the undefined bit
(In reply to Richard Biener from comment #7)
> === BB 2
> Imports:
Successfully bootstrapped & regrtested on x86_64-pc-linux-gnu.
Pushed to trunk as 347682ea4637c57c386908d6e1aa52e4efaace53.
gcc/analyzer/ChangeLog:
* program-state.cc (sm_state_map::dump): Use default_tree_printer
as format decoder.
---
gcc/analyzer/program-state.cc | 1 +
1 file
Hi All,
This test hopefully fixes all the remaining target specific test issues by
1: Unrolling all add testcases by 16 using pragma GCC unroll
2. On armhf use Adv.SIMD instead of MVE to test. MVE's autovec is too incomplete
to be a general test target.
3. Add appropriate vect_ and float
On Thu, Nov 4, 2021 at 1:51 PM Martin Liška wrote:
>
> On 11/2/21 17:45, Richard Biener wrote:
> > On Tue, Nov 2, 2021 at 4:11 PM Martin Liška wrote:
> >>
> >> On 11/2/21 15:33, Richard Biener wrote:
> >>> I think -gtoggle matches a Defered option and thus should be processed
> >>> in
On Wed, 3 Nov 2021, Tamar Christina wrote:
> Hi,
>
> I have addressed all the feedback and updated patch attached:
>
> Bootstrapped Regtested on aarch64-none-linux-gnu,
> x86_64-pc-linux-gnu and no regressions.
>
> Ok for master?
>
> Thanks,
> Tamar
>
> gcc/ChangeLog:
>
> * match.pd:
On Wed, Nov 3, 2021 at 2:29 PM Xionghu Luo wrote:
>
>
>
> On 2021/10/29 19:48, Richard Biener wrote:
> > I'm talking about the can_sm_ref_p call, in that context 'loop' will
> > be the outermost loop of
> > interest, and we are calling this for all stores in a loop. We're doing
> >
> > +bool
> >
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103042
Tamar Christina changed:
What|Removed |Added
Ever confirmed|0 |1
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101981
Martin Liška changed:
What|Removed |Added
Resolution|--- |WORKSFORME
Status|NEW
On 11/2/21 17:45, Richard Biener wrote:
On Tue, Nov 2, 2021 at 4:11 PM Martin Liška wrote:
On 11/2/21 15:33, Richard Biener wrote:
I think -gtoggle matches a Defered option and thus should be processed
in handle_common_deferred_options.
Well, that's quite problematic as I
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103072
--- Comment #2 from Martin Liška ---
Or we can alternatively merge all the case blocks into one..
On Thu, Nov 04, 2021 at 12:39:34PM +, Iain Sandoe wrote:
> Bootstrap succeeded with Apple clang-503.0.40 (Xcode 5.1.1) on macOS 10.8
> which is the earliest version I expect to work (previous xcode impl. have more
> C++11 incompatibilities). So OK from a Darwin PoV.
>
> The other reported
On Thu, Nov 4, 2021 at 12:57 PM Segher Boessenkool
wrote:
>
> On Fri, Oct 29, 2021 at 09:32:21AM +0200, Richard Biener via Gcc-patches
> wrote:
> > On Fri, Oct 29, 2021 at 2:42 AM Bernhard Reutner-Fischer via
> > Gcc-patches wrote:
> > >
> > > From: Bernhard Reutner-Fischer
> > >
> > > Bump
On Thu, Nov 4, 2021 at 12:57 PM Segher Boessenkool
wrote:
>
> On Fri, Oct 29, 2021 at 09:32:21AM +0200, Richard Biener via Gcc-patches
> wrote:
> > On Fri, Oct 29, 2021 at 2:42 AM Bernhard Reutner-Fischer via
> > Gcc-patches wrote:
> > >
> > > From: Bernhard Reutner-Fischer
> > >
> > > Bump
On 11/4/21 13:37, Jakub Jelinek wrote:
On Thu, Nov 04, 2021 at 01:25:43PM +0100, Martin Liška wrote:
diff --git a/libsanitizer/asan/asan_mapping.h b/libsanitizer/asan/asan_mapping.h
index 4b0037fced3..e5a7f2007ae 100644
--- a/libsanitizer/asan/asan_mapping.h
+++
Hi Jakub,
> On 4 Nov 2021, at 10:05, Jakub Jelinek wrote:
>
> On Tue, Jul 06, 2021 at 11:17:55AM +0100, Iain Sandoe wrote:
The addition of the CTOR is the fix for the C++ compile fail in the PR,
the conditional is
only there because the same header is compiled by C and C++.
>>>
On Thu, Nov 04, 2021 at 01:25:43PM +0100, Martin Liška wrote:
> diff --git a/libsanitizer/asan/asan_mapping.h
> b/libsanitizer/asan/asan_mapping.h
> index 4b0037fced3..e5a7f2007ae 100644
> --- a/libsanitizer/asan/asan_mapping.h
> +++ b/libsanitizer/asan/asan_mapping.h
> @@ -165,7 +165,7 @@ static
Sending the patch in a separate thread.
Ready for master?
Cheers,
Martin
gcc/ChangeLog:
* config/rs6000/rs6000.c (rs6000_override_options_after_change):
Do not set flag_rename_registers, it's already enabled with
EnabledBy(funroll-loops).
Use EnabledBy for
I've now committed the patch to rework the vector costs hooks --
thanks to Richard for the review.
This patch moves more code into aarch64_vector_costs and reuses
some of the information that is now available in the base class.
I'm planing to significantly rework this code, with more hooks
into
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103075
Richard Biener changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103075
--- Comment #3 from CVS Commits ---
The master branch has been updated by Richard Biener :
https://gcc.gnu.org/g:d13603501680fcdbb933cb086cd01fcc39be1908
commit r12-4898-gd13603501680fcdbb933cb086cd01fcc39be1908
Author: Richard Biener
Date:
On Thu, Nov 4, 2021 at 1:20 AM Jakub Jelinek wrote:
>
> On Thu, Nov 04, 2021 at 06:43:26AM +0100, Gerald Pfeifer wrote:
> > On Tue, 2 Nov 2021, H.J. Lu wrote:
> > > On Tue, Nov 2, 2021 at 5:11 AM Jakub Jelinek wrote:
> > >> include/md5.h is a header we have control over, can't we just add to it
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103079
--- Comment #8 from Richard Biener ---
Btw, I find the vrp-details dump not really useful with all the ranger
"debug" appearing _after_ the folding of stmts. Can we instead have
this somehow interleaved?
On 11/4/21 12:55, Segher Boessenkool wrote:
On Fri, Oct 29, 2021 at 09:32:21AM +0200, Richard Biener via Gcc-patches wrote:
On Fri, Oct 29, 2021 at 2:42 AM Bernhard Reutner-Fischer via
Gcc-patches wrote:
From: Bernhard Reutner-Fischer
Bump required DejaGnu version to 1.5.3 (or later).
Ok
On 11/4/21 12:55, Segher Boessenkool wrote:
On Fri, Oct 29, 2021 at 09:32:21AM +0200, Richard Biener via Gcc-patches wrote:
On Fri, Oct 29, 2021 at 2:42 AM Bernhard Reutner-Fischer via
Gcc-patches wrote:
From: Bernhard Reutner-Fischer
Bump required DejaGnu version to 1.5.3 (or later).
Ok
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103079
--- Comment #7 from Richard Biener ---
=== BB 2
Imports: b.0_1 t_4(D)
Exports: b.0_1 t_4(D) _6
_6 : b.0_1(I) t_4(D)(I)
t_4(D) UNDEFINED
[local count: 176285970]:
b.0_1 = b;
_6 = b.0_1 | t_4(D);
> > + if (!TYPE_UNSIGNED (TREE_TYPE (orig_use_lhs)))
> > + return false;
> > + if (SSA_NAME_OCCURS_IN_ABNORMAL_PHI (orig_use_lhs))
> > + return false;
> > + if (EDGE_COUNT (phi_bb->preds) != 4)
> > + return false;
> > + if (!TYPE_UNSIGNED (TREE_TYPE (orig_use_lhs)))
> > +
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102967
jbeulich at suse dot com changed:
What|Removed |Added
CC||jbeulich at suse dot com
---
On Wed, 27 Oct 2021, Richard Sandiford wrote:
> Richard Biener writes:
> > This refactors the main loop analysis part in vect_analyze_loop,
> > re-purposing the existing vect_reanalyze_as_main_loop for this
> > to reduce code duplication. Failure flow is a bit tricky since
> > we want to
On Fri, Oct 29, 2021 at 09:32:21AM +0200, Richard Biener via Gcc-patches wrote:
> On Fri, Oct 29, 2021 at 2:42 AM Bernhard Reutner-Fischer via
> Gcc-patches wrote:
> >
> > From: Bernhard Reutner-Fischer
> >
> > Bump required DejaGnu version to 1.5.3 (or later).
> > Ok for trunk?
>
> OK.
If we
On Fri, Oct 29, 2021 at 09:32:21AM +0200, Richard Biener via Gcc-patches wrote:
> On Fri, Oct 29, 2021 at 2:42 AM Bernhard Reutner-Fischer via
> Gcc-patches wrote:
> >
> > From: Bernhard Reutner-Fischer
> >
> > Bump required DejaGnu version to 1.5.3 (or later).
> > Ok for trunk?
>
> OK.
If we
On Tue, Oct 19, 2021 at 04:43:40PM +0200, Martin Liška wrote:
> On 10/19/21 16:23, Segher Boessenkool wrote:
> >On Fri, Oct 15, 2021 at 05:24:32PM +0200, Martin Liška wrote:
> >>On 10/14/21 17:10, Bill Schmidt via Gcc-patches wrote:
> >>>Looks like you got your parentheses wrong here.
> >>
>
On Wed, 27 Oct 2021 at 09:27, Jay Feldblum via Libstdc++ <
libstd...@gcc.gnu.org> wrote:
> From: yfeldblum
>
> The stdout stream is reserved for output intentionally produced by the
> application. Assertion failures and other forms of logging must be
> emitted to stderr, not to stdout.
>
> It is
On Thu, Nov 4, 2021 at 11:05 AM Martin Liška wrote:
>
> On 11/2/21 16:56, Sandra Loosemore wrote:
> > On 11/2/21 9:20 AM, Martin Liška wrote:
> >> On 11/2/21 15:48, Sandra Loosemore wrote:
> >>> On 11/2/21 2:51 AM, Martin Liška wrote:
> On 11/2/21 00:56, Sandra Loosemore wrote:
> > I'll
On Thu, 4 Nov 2021, Jakub Jelinek wrote:
> Hi!
>
> When users don't use constexpr everywhere in initialization of namespace
> scope non-comdat vars and the initializers aren't constant when FE is
> looking at them, the FE performs dynamic initialization of those variables.
> But after inlining
Hi,
As the discussions and the testing result under the main thread, this
patch would be safe.
Ping for this:
https://gcc.gnu.org/pipermail/gcc-patches/2021-September/580357.html
BR,
Kewen
>
> on 2021/9/28 下午4:13, Kewen.Lin via Gcc-patches wrote:
>> Hi,
>>
>> As the discussion in PR102347,
Hi,
Gentle ping this patch:
https://gcc.gnu.org/pipermail/gcc-patches/2021-September/578552.html
One related patch [1] is ready to commit, whose test cases rely on
this patch if no changes are applied to them.
[1] https://gcc.gnu.org/pipermail/gcc-patches/2021-September/579658.html
BR,
Kewen
Hi,
Gentle ping this:
https://gcc.gnu.org/pipermail/gcc-patches/2021-September/580358.html
BR,
Kewen
>> on 2021/9/28 下午4:16, Kewen.Lin via Gcc-patches wrote:
>>> Hi,
>>>
>>> This patch follows the discussions here[1][2], where Segher
>>> pointed out the existing way to guard the extra
Hi,
Gentle ping this:
https://gcc.gnu.org/pipermail/gcc-patches/2021-June/572555.html
BR,
Kewen
> on 2021/6/11 下午9:16, Kewen.Lin via Gcc-patches wrote:
>> Hi Segher,
>>
>> Thanks for the review!
>>
>> on 2021/6/10 上午4:17, Segher Boessenkool wrote:
>>> Hi!
>>>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103062
Aldy Hernandez changed:
What|Removed |Added
CC||aldyh at gcc dot gnu.org
101 - 200 of 268 matches
Mail list logo
