On Mon, 29 Nov 2021, Martin Sebor wrote:
> On 11/29/21 11:53 AM, Martin Sebor wrote:
> > On 11/29/21 6:09 AM, Richard Biener via Gcc-patches wrote:
> >> This removes more cases that appear when bootstrap with
> >> -Wunreachable-code-return progresses.
> >>
> > ...
> >> diff --git
On Mon, Nov 29, 2021 at 6:20 PM Andrew MacLeod via Gcc-patches
wrote:
>
> I need to adjust the original patch, I shouldn't have continued the loop
> when dealing with equivalences.An equivalence is not the same as an
> undefined value... we might be able to ignore the range from it for
>
On Mon, Nov 29, 2021 at 4:40 PM Richard Sandiford
wrote:
>
> Sorry for the slow response, was away last week.
>
> Richard Biener writes:
> > On Wed, Nov 10, 2021 at 1:50 PM Richard Sandiford via Gcc-patches
> > wrote:
> >>
> >> This patch uses information about internal functions to
On Mon, Nov 29, 2021 at 4:40 PM Martin Sebor wrote:
>
> On 11/25/21 3:18 AM, Richard Biener wrote:
> > On Mon, Aug 30, 2021 at 10:06 PM Martin Sebor via Gcc-patches
> > wrote:
> >>
> >> The predicate analysis subset of the tree-ssa-uninit pass isn't
> >> necessarily specific to the detection of
On Mon, Nov 29, 2021 at 4:24 PM Aldy Hernandez wrote:
>
> On Mon, Nov 29, 2021 at 3:48 PM Richard Biener
> wrote:
> >
> > On Mon, Nov 29, 2021 at 3:39 PM Jeff Law wrote:
> > >
> > >
> > >
> > > On 11/29/2021 7:00 AM, Aldy Hernandez via Gcc-patches wrote:
> > > > As discussed in the PR. The
Hi Segher,
on 2021/11/30 上午6:06, Segher Boessenkool wrote:
> Hi!
>
> On Tue, Sep 28, 2021 at 04:16:04PM +0800, Kewen.Lin wrote:
>> This patch follows the discussions here[1][2], where Segher
>> pointed out the existing way to guard the extra penalized
>> cost for strided/elementwise loads with a
Hi Segher,
on 2021/11/30 上午8:16, Segher Boessenkool wrote:
> Hi!
>
> On Tue, Sep 28, 2021 at 04:13:40PM +0800, Kewen.Lin wrote:
>> PR target/102347
>> * config/rs6000/rs6000-call.c (rs6000_builtin_decl): Remove builtin
>> mask check.
>
> (Don't wrap lines early please).
>
On 11/29/21 11:31, Jakub Jelinek wrote:
Hi!
P1272R4 has added to the std::byteswap new stuff to me quite unrelated
clarification for std::bit_cast.
std::bit_cast is already in C++20 though and std::byteswap is a new
C++23 feature, it is unclear to me if that bit_cast addition in there
is really
On Tue, Nov 30, 2021 at 5:21 AM Uros Bizjak wrote:
>
> On Mon, Nov 29, 2021 at 10:48 AM Hongtao Liu wrote:
> >
> > On Mon, Nov 29, 2021 at 3:53 PM Uros Bizjak wrote:
> > >
> > > On Mon, Nov 29, 2021 at 2:32 AM liuhongt wrote:
> > > >
> > > > There're several failures reported in [1]:
> > > >
On 11/26/21 5:18 AM, Richard Biener via Gcc-patches wrote:
This implements a subset of -Wunreachable-code, unreachable code
after a return stmt. Contrary to the previous attemt at CFG
construction time this implements the bits during GIMPLE lowering
where there are still all GIMPLE return stmts
After making sure the vector is large enough, we use a reference to the
object through the rest of the function. One path however requests the
def chain for a dependant ssa-name, and if that request caused a resize,
then our reference is no longer valid. On this path, simply use the
object
On 11/26/21 04:33, Jakub Jelinek wrote:
Hi!
stringify_arg uses pfile->u_buff to create the string literal.
Unfortunately, paste_tokens -> _cpp_lex_direct -> lex_number ->
_cpp_unaligned_alloc
can in some cases use pfile->u_buff too, which results in losing everything
prepared for the string
Hi!
On Tue, Sep 28, 2021 at 04:13:40PM +0800, Kewen.Lin wrote:
> PR target/102347
> * config/rs6000/rs6000-call.c (rs6000_builtin_decl): Remove builtin
> mask check.
(Don't wrap lines early please).
Okay for trunk and all backports. Thanks!
Segher
Hi!
On Mon, Oct 11, 2021 at 02:30:42PM +0800, Kewen.Lin wrote:
> > If we do need a band-aid for 10 and 11 (and we do as far as I can see),
> > I'd like to see one for just MMA there, and let all other badness fade
> > into history. Unless you can convince me (in the patch / commit
> > message)
Commit r12-5424-gf573d35147ca8433c102e1721d8c99fc432cb44b fixed a false
positive from -Wanalyzer-malloc-leak due to overzealous state merging,
erroneously merging two different svalues bound to a particular part
of the store when one has sm-state.
A further case was discovered by the reporter of
Jeff,
Sorry for bringing back this thread.
Quick question, you mentioned checking the TYPE_PRECISION to make sure the type
is a canonical Boolean type (and not a fancy signed/unsigned Boolean type from
Ada Andrew mentioned).
But I noticed that truth_valued_p does already check for:
(if
Peter,
Thanks a lot for the patch.
Richard, how do you think of the patch?
(The major concern for me is:
With the current patch proposed by Peter, we will generate the call to
.DEFERRED_INIT for a variable with OPAQUE_TYPE during gimplification phase,
However, if this
On 11/29/21 06:24, Jakub Jelinek wrote:
Hi!
Jonathan mentioned on IRC that:
"Accept P1949R7 (C++ Identifier Syntax using Unicode Standard Annex 31) as
a Defect Report and apply the changes therein to the C++ working paper."
while I've actually implemented it only for -std={gnu,c}++{23,2b}.
As
On 11/27/21 03:52, Jakub Jelinek wrote:
On Wed, Nov 24, 2021 at 11:42:28PM +0100, Jakub Jelinek via Gcc-patches wrote:
I'm surprised the source_location::current handling would be needed; why do
calls to that function live long enough for us to walk into the ADDR_EXPR
here? Maybe we should
On 11/21/21 21:51, Will Wray via Gcc-patches wrote:
This second patch completes the work of the first 'array-copy' patch to
provide first-cut implementations of all P1997 features. It adds:
* Assignments to arrays from array values,a = b;
* Placeholder auto in array declarations,
Hi!
On Fri, Jun 11, 2021 at 09:16:21PM +0800, Kewen.Lin wrote:
> >> +/* Should pick up the lowest luid if the references
> >> + are in the same block. */
> >> +if (label_tick == rsp->last_set_table_tick
> >> +&& rsp->last_set_table_luid > insn_luid)
> >> +
Hi!
On Tue, Sep 28, 2021 at 04:16:04PM +0800, Kewen.Lin wrote:
> This patch follows the discussions here[1][2], where Segher
> pointed out the existing way to guard the extra penalized
> cost for strided/elementwise loads with a magic bound does
> not scale.
>
> The way with nunits * stmt_cost
Dear all,
another trivial and obvious one, discovered by Gerhard.
We can have a NULL pointer dereference simplifying MINLOC/MAXLOC
on an array that was not properly declared.
OK for mainline / affected 11-branch after regtesting completes?
Thanks,
Harald
From
Sorry for dropping the ball on testing the patch from the bugzilla!
The following patch fixes the ICE reported in the bugzilla on the pre-existing
gcc testsuite test case, bootstraps and shows no testsuite regressions
on powerpc64le-linux. Ok for trunk?
Peter
For -ftrivial-auto-var-init=*,
Dear all,
a trivial one: we need to check the type of the SUB argument
to the coarray IMAGE_INDEX intrinsic. It has to be an array
of type integer.
Patch by Steve Kargl.
Regtested on x86_64-pc-linux-gnu. OK for mainline?
Thanks,
Harald
From 58140e3cf97aedc5c9f3b3e6519027334cdc3213 Mon Sep
On Mon, Nov 29, 2021 at 10:48 AM Hongtao Liu wrote:
>
> On Mon, Nov 29, 2021 at 3:53 PM Uros Bizjak wrote:
> >
> > On Mon, Nov 29, 2021 at 2:32 AM liuhongt wrote:
> > >
> > > There're several failures reported in [1]:
> > > 1. unsupported instruction `pextrw` for "pextrw $0, %xmm31, 16(%rax)"
Pushed to wwwdocs.
---
htdocs/gcc-12/changes.html | 7 ---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/htdocs/gcc-12/changes.html b/htdocs/gcc-12/changes.html
index b8524f47..10ac025f 100644
--- a/htdocs/gcc-12/changes.html
+++ b/htdocs/gcc-12/changes.html
@@ -289,9 +289,9
Hi Tobias, all,
Am 29.11.21 um 21:56 schrieb Tobias Burnus:
The problem is that the standard does not really state what the bounds
are :-(
I sort of expected that comment...
Usually, it ends up referring to LBOUND (with wordings like "each lower
bound equal to the corresponding element of
On Sat, 27 Nov 2021, chenglulu wrote:
> + if (p_arch_native)
> + fatal_error (UNKNOWN_LOCATION,
> +"Unknown FPU type %<0x%x%>, "
> +"%<-m" OPTSTR_ARCH "=" STR_CPU_NATIVE "%> failed",
Diagnostics should not start with an uppercase letter (unless
Hi Harald, hi Chung-Lin,
On 29.11.21 21:21, Harald Anlauf wrote:
I think you need to check the following:
allocate(c, source=h(3))
write(*,*) lbound(c,1), ubound(c,1) ! prints 1 3
...
pure function h(i) result(r)
integer, value, intent(in) :: i
integer, allocatable :: r(:)
On Mon, Nov 29, 2021 at 7:14 PM Roger Sayle wrote:
>
>
> Hi Uros,
> Many thanks for the review. Here's a revised version of the patch
> incorporating all of your suggestions. This has been (re)tested on
> x86_64-pc-linux-gnu with make bootstrap and make -k check,
> both with and without
Hi Chung-Lin,
Am 29.11.21 um 15:25 schrieb Chung-Lin Tang:
This patch by Tobias, fixes a case of setting array low-bounds, found
for particular uses of SOURCE=/MOLD=.
For example:
program A_M
implicit none
real, dimension (:), allocatable :: A, B
allocate (A(0:5))
call Init (A)
Am 29.11.21 um 12:28 schrieb Richard Biener via Fortran:
This fixes an appearant mistake in gfc_insert_parameter_exprs.
Yes, that looks pretty much like a missed cleanup and fix during
development. CC'ing Paul.
Bootstrap / regtest pending on x86_64-unknown-linux-gnu.
OK?
LGTM if it
* Fāng-ruì Sòng:
> PING^3
I think the core issue with this patch is like this:
* I do not want to commit glibc to a public API that disallows future
changes to the way we allocate static TLS. While static TLS objects
cannot move in memory, the extent of the static TLS area (minimum and
On 11/29/21 11:53 AM, Martin Sebor wrote:
On 11/29/21 6:09 AM, Richard Biener via Gcc-patches wrote:
This removes more cases that appear when bootstrap with
-Wunreachable-code-return progresses.
...
diff --git a/gcc/sel-sched-ir.h b/gcc/sel-sched-ir.h
index 8ee0529d5a8..18e03c4cb96 100644
On 11/29/21 6:09 AM, Richard Biener via Gcc-patches wrote:
This removes more cases that appear when bootstrap with
-Wunreachable-code-return progresses.
...
diff --git a/gcc/sel-sched-ir.h b/gcc/sel-sched-ir.h
index 8ee0529d5a8..18e03c4cb96 100644
--- a/gcc/sel-sched-ir.h
+++
Hi,
On Sat, Nov 27 2021, Jan Hubicka wrote:
>> Hi,
>>
>> IPA_JF_ANCESTOR jump functions are constructed also when the formal
>> parameter of the caller is first checked whether it is NULL and left
>> as it is if it is NULL, to accommodate C++ casts to an ancestor class.
>>
>> The jump function
On Mon, Nov 29, 2021 at 9:48 AM Jeff Law wrote:
>
>
>
> On 11/28/2021 6:34 PM, Eric Gallager via Gcc-patches wrote:
> > The attached patch allows users to specify a path to their `etags`
> > executable for use when doing `make tags`, which is meant to close PR
> > other/103021:
> Hi,
>
> PR 103449 revealed that when I was storing result of one hash_map
> lookup into another entry in the hash_map, I was still accessing the
> entry in the table, which meanwhile could get reallocated, making the
> accesses invalid-after-free.
>
> Fixed with the following, which also
Hi,
PR 103449 revealed that when I was storing result of one hash_map
lookup into another entry in the hash_map, I was still accessing the
entry in the table, which meanwhile could get reallocated, making the
accesses invalid-after-free.
Fixed with the following, which also simplifies the return
Hi Uros,
Many thanks for the review. Here's a revised version of the patch
incorporating all of your suggestions. This has been (re)tested on
x86_64-pc-linux-gnu with make bootstrap and make -k check,
both with and without --target_board=unix{-m32}, with no new
failures. Ok for mainline?
Hi Rasmus,
> On 1 Nov 2021, at 10:34, Rasmus Villemoes wrote:
>
> libgcc/
> * config/vxcrtstuff.c: Undefine caddr_t, pid_t, rlim_t,
> ssize_t and vfork after including auto-host.h.
Ok, thanks;
On 11/25/21 12:57 AM, Richard Biener wrote:
On Wed, 24 Nov 2021, Martin Sebor wrote:
On 11/24/21 8:21 AM, Richard Biener via Gcc-patches wrote:
This resurrects -Wunreachable-code and implements a warning for
trivially unreachable code as of CFG construction. Most problematic
with this is the
I need to adjust the original patch, I shouldn't have continued the loop
when dealing with equivalences. An equivalence is not the same as an
undefined value... we might be able to ignore the range from it for
calculation purposes, but we cannot ignore the fact that it is a
different
Hi!
On Wed, Sep 01, 2021 at 02:55:51PM +0800, Kewen.Lin wrote:
> This patch is to fix the inconsistent behaviors for non-LTO mode
> and LTO mode. As Martin pointed out, currently the function
> rs6000_can_inline_p simply makes it inlinable if callee_tree is
> NULL, but it's wrong, we should use
Hi!
P1272R4 has added to the std::byteswap new stuff to me quite unrelated
clarification for std::bit_cast.
std::bit_cast is already in C++20 though and std::byteswap is a new
C++23 feature, it is unclear to me if that bit_cast addition in there
is really meant for C++23 and later only (e.g.
We're using a temporary range cache while computing ranges for PHIs to
make sure the real cache doesn't get set until all PHIs are computed.
With the ltrans beast in LTO mode this causes undue overhead.
Since we already have a bitmap to indicate whether there's a cache
entry, we can avoid the
Ping:
https://gcc.gnu.org/pipermail/gcc-patches/2021-November/585180.html
On 11/22/21 4:54 PM, Martin Sebor wrote:
In an effort to avoid false positives while still detecting
certain out-of-bounds accesses the warning code that handles
PHI nodes chooses the operand with the most space remaining
On 11/29/2021 8:03 AM, Richard Biener via Gcc-patches wrote:
This cleans up unreachable code diagnosed by -Wunreachable-code-ctrl.
It largely follows the previous series but discovers a few extra
cases, namely dead code after break or continue or loops without
exits.
Bootstrapped on
Ping:
https://gcc.gnu.org/pipermail/gcc-patches/2021-November/583735.html
On 11/22/21 9:41 AM, Martin Sebor wrote:
Ping:
https://gcc.gnu.org/pipermail/gcc-patches/2021-November/583735.html
On 11/15/21 9:49 AM, Martin Sebor wrote:
Ping for the following cleanup patch:
Sorry for the slow response, was away last week.
Richard Biener writes:
> On Wed, Nov 10, 2021 at 1:50 PM Richard Sandiford via Gcc-patches
> wrote:
>>
>> This patch uses information about internal functions to canonicalize
>> the argument order of calls.
>>
>> Tested on aarch64-linux-gnu and
On 11/25/21 3:18 AM, Richard Biener wrote:
On Mon, Aug 30, 2021 at 10:06 PM Martin Sebor via Gcc-patches
wrote:
The predicate analysis subset of the tree-ssa-uninit pass isn't
necessarily specific to the detection of uninitialized reads.
Suitably parameterized, the same core logic could be
Richard Biener via Gcc-patches writes:
> On Tue, Nov 16, 2021 at 5:24 PM Richard Sandiford
> wrote:
>>
>> Richard Biener via Gcc-patches writes:
>> > On Wed, Nov 10, 2021 at 1:48 PM Richard Sandiford via Gcc-patches
>> > wrote:
>> >>
>> >> This patch extends the reduction code to handle calls.
On Mon, Nov 29, 2021 at 3:48 PM Richard Biener
wrote:
>
> On Mon, Nov 29, 2021 at 3:39 PM Jeff Law wrote:
> >
> >
> >
> > On 11/29/2021 7:00 AM, Aldy Hernandez via Gcc-patches wrote:
> > > As discussed in the PR. The code makes no difference, so whatever test
> > > we added this special case
There are cases where a default option value is -1 and
auto-detection happens in e.g. target.
Do not print these options. Leads to the following diff:
- -fdelete-null-pointer-checks [enabled]
+ -fdelete-null-pointer-checks
@@ -332 +332 @@
-
This cleans up unreachable code diagnosed by -Wunreachable-code-ctrl.
It largely follows the previous series but discovers a few extra
cases, namely dead code after break or continue or loops without
exits.
Bootstrapped on x86_64-unknown-linux-gnu, testing in progress.
Richard.
2021-11-29
On Mon, Nov 29, 2021 at 3:39 PM Jeff Law wrote:
>
>
>
> On 11/29/2021 7:00 AM, Aldy Hernandez via Gcc-patches wrote:
> > As discussed in the PR. The code makes no difference, so whatever test
> > we added this special case for has been fixed or is being papered over.
> > I think we should fix
On 11/28/2021 6:34 PM, Eric Gallager via Gcc-patches wrote:
The attached patch allows users to specify a path to their `etags`
executable for use when doing `make tags`, which is meant to close PR
other/103021: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103021
I based this patch off of this
On 11/29/2021 7:00 AM, Aldy Hernandez via Gcc-patches wrote:
As discussed in the PR. The code makes no difference, so whatever test
we added this special case for has been fixed or is being papered over.
I think we should fix any fall out upstream.
[Unless Andrew can remember why we added
On 11/29/2021 4:26 AM, Richard Biener via Gcc-patches wrote:
This fixes an issue discovered by -Wunreachable-code-return
Bootstrap / regtest pending on x86_64-unknown-linux-gnu, OK?
2021-11-29 Richard Biener
* read-rtl-function.c (function_reader::read_rtx_operand):
This patch by Tobias, fixes a case of setting array low-bounds, found
for particular uses of SOURCE=/MOLD=.
For example:
program A_M
implicit none
real, dimension (:), allocatable :: A, B
allocate (A(0:5))
call Init (A)
contains
subroutine Init ( A )
real, dimension ( 0 : ), intent
As discussed in the PR. The code makes no difference, so whatever test
we added this special case for has been fixed or is being papered over.
I think we should fix any fall out upstream.
[Unless Andrew can remember why we added this and it still applies.]
Tested on x86-64 Linux.
OK for trunk?
This avoids a -Wunreachable-code-return diagnostic about
two consecutive returns by placing the return in the appropriate
conditional block.
OK?
Thanks,
Richard.
2021-11-29 Richard Biener
libstd++-v3/
* src/c++17/fs_ops.cc (fs::equivalent): Move return stmt inside #else.
---
This removes more cases that appear when bootstrap with
-Wunreachable-code-return progresses.
Bootstrapped on x86_64-unknown-linux-gnu, testing in progress.
Richard.
2021-11-29 Richard Biener
* config/i386/i386.c (ix86_shift_rotate_cost): Remove
unreachable return.
*
This is the original binutils bugzilla report,
https://sourceware.org/bugzilla/show_bug.cgi?id=28509
And this is the first version of the proposed binutils patch,
https://sourceware.org/pipermail/binutils/2021-November/118398.html
After applying the binutils patch, I get the the unexpected error
On 11/26/21 09:12, Richard Biener wrote:
On Wed, Nov 24, 2021 at 3:32 PM Martin Liška wrote:
On 11/24/21 15:14, Martin Liška wrote:
It likely miscompiles gcc.dg/loop-unswitch-5.c, working on that..
Fixed that in the updated version.
Function level comments need updating it seems.
I've
On Mon, 29 Nov 2021, Tamar Christina wrote:
> Hi All,
>
> Following the previous bugfix this addresses the cosmetic and test issues.
>
> The vector tests are moved to vect and the scalar are left where they are.
>
> Bootstrapped Regtested x86_64-pc-linux-gnu and no regressions.
> Tested with
Hi All,
Following the previous bugfix this addresses the cosmetic and test issues.
The vector tests are moved to vect and the scalar are left where they are.
Bootstrapped Regtested x86_64-pc-linux-gnu and no regressions.
Tested with -m32/-mno-sse and no issues.
Ok for master?
Thanks,
Tamar
On Mon, Nov 29, 2021 at 3:24 AM Jakub Jelinek wrote:
>
> Hi!
>
> On Tue, Aug 31, 2021 at 10:05:58AM +0200, Jakub Jelinek via Gcc-patches wrote:
> > This is an incremental patch to
> > https://gcc.gnu.org/pipermail/gcc-patches/2021-August/578447.html
> > for x86_64 ABI.
> > For zero-width
This fixes an appearant mistake in gfc_insert_parameter_exprs.
Bootstrap / regtest pending on x86_64-unknown-linux-gnu.
OK?
Thanks,
Richard.
2021-11-29 Richard Biener
gcc/fortran/
* decl.c (gfc_insert_parameter_exprs): Only return after
resetting type_param_spec_list.
---
This fixes an issue discovered by -Wunreachable-code-return
Bootstrap / regtest pending on x86_64-unknown-linux-gnu, OK?
2021-11-29 Richard Biener
* read-rtl-function.c (function_reader::read_rtx_operand):
Return only after resetting m_in_call_function_usage.
---
Hi!
Jonathan mentioned on IRC that:
"Accept P1949R7 (C++ Identifier Syntax using Unicode Standard Annex 31) as
a Defect Report and apply the changes therein to the C++ working paper."
while I've actually implemented it only for -std={gnu,c}++{23,2b}.
As the C++98 rules were significantly
On 18/11/2021 11:05, Richard Biener wrote:
+ (if (!flag_trapping_math
+ && direct_internal_fn_supported_p (IFN_TRUNC, type,
+OPTIMIZE_FOR_BOTH))
+ (IFN_TRUNC @0)
#endif
does IFN_FTRUNC_INT preserve the same exceptions as
On Sun, 28 Nov 2021, Jeff Law wrote:
>
>
> On 11/25/2021 6:33 AM, Richard Biener via Gcc-patches wrote:
> > It seems to be a style to place gcc_unreachable () after a
> > switch that handles all cases with every case returning.
> > Those are unreachable (well, yes!), so they will be elided
> >
Hi!
On Tue, Aug 31, 2021 at 10:05:58AM +0200, Jakub Jelinek via Gcc-patches wrote:
> This is an incremental patch to
> https://gcc.gnu.org/pipermail/gcc-patches/2021-August/578447.html
> for x86_64 ABI.
> For zero-width bitfields current GCC classify_argument does:
> if
On Sun, 28 Nov 2021, Jeff Law wrote:
>
>
> On 11/25/2021 7:16 AM, Richard Biener via Gcc-patches wrote:
> > This removes unreachable return statements as diagnosed by
> > the -Wunreachable-code patch. Some cases are more obviously
> > an improvement than others - in fact some may get you the
On Mon, Nov 29, 2021 at 3:53 PM Uros Bizjak wrote:
>
> On Mon, Nov 29, 2021 at 2:32 AM liuhongt wrote:
> >
> > There're several failures reported in [1]:
> > 1. unsupported instruction `pextrw` for "pextrw $0, %xmm31, 16(%rax)"
> > %vpextrw should be used in output templates.
> > 2. ICE in
> -Original Message-
> From: Richard Biener
> Sent: Monday, November 29, 2021 9:02 AM
> To: Tamar Christina
> Cc: gcc-patches@gcc.gnu.org; nd ; j...@tachyum.com;
> Richard Sandiford
> Subject: Re: [PATCH]middle-end cse: Make sure duplicate elements are not
> entered into the equivalence
When creating forwarders in CD-DCE we have to avoid creating loops
where we formerly did not consider those because of abnormal
predecessors. At this point simply excuse us when there are any
abnormal predecessors.
Bootstrapped and tested on x86_64-unknown-linux-gnu, pushed.
2021-11-29 Richard
On 11/27/21 16:56, Jan Hubicka via Gcc-patches wrote:
Hi,
Profile-report was never properly updated after switch to new profile
representation. This patch fixes the way profile mismatches are
calculated: we used to collect separately count and freq mismatches,
while now we have only counts &
This middle-end patch is inspired by Richard Biener's until-wrap
loop example in PR tree-optimization/101145.
unsigned foo(unsigned val, unsigned start)
{
unsigned cnt = 0;
for (unsigned i = start; i > val; ++i)
cnt++;
return cnt;
}
For this loop, the tree optimizers currently
On Mon, 29 Nov 2021, Tamar Christina wrote:
> Hi All,
>
> CSE uses equivalence classes to keep track of expressions that all have the
> same
> values at the current point in the program.
>
> Normal equivalences through SETs only insert and perform lookups in this set
> but
> equivalence
On Mon, Nov 29, 2021 at 1:57 AM Andrew Pinski via Gcc-patches
wrote:
>
> On Sun, Nov 28, 2021 at 12:25 PM Jeff Law via Gcc-patches
> wrote:
> >
> >
> >
> > On 11/28/2021 10:56 AM, apinski--- via Gcc-patches wrote:
> > > From: Andrew Pinski
> > >
> > > This just adds a simplification to
On Mon, Nov 29, 2021 at 9:53 AM Richard Biener
wrote:
>
> On Mon, Nov 29, 2021 at 1:42 AM Andrew Pinski via Gcc-patches
> wrote:
> >
> > On Sun, Nov 28, 2021 at 12:14 PM Jeff Law via Gcc-patches
> > wrote:
> > >
> > >
> > >
> > > On 11/27/2021 7:49 PM, apinski--- via Gcc-patches wrote:
> > > >
On Mon, Nov 29, 2021 at 1:42 AM Andrew Pinski via Gcc-patches
wrote:
>
> On Sun, Nov 28, 2021 at 12:14 PM Jeff Law via Gcc-patches
> wrote:
> >
> >
> >
> > On 11/27/2021 7:49 PM, apinski--- via Gcc-patches wrote:
> > > From: Andrew Pinski
> > >
> > > Even though I cannot reproduce the ICE any
85 matches
Mail list logo
