On 11/26/2021 12:53 AM, Richard Biener via Gcc-patches wrote:
This restores the semantics of can_be_invalidated_p to the original
semantics of the function this was split out from tree-ssa-uninit.c.
The current semantics only ever look at the first predicate which
cannot be correct.
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 idea
to replace them with gcc_unreachable () instead,
On Sun, Nov 28, 2021 at 3:02 PM Roger Sayle wrote:
>
>
> This patch builds on the recent improvements to TImode rotations (and
> Jakub's fixes to shldq/shrdq patterns). Now that expanding a TImode
> rotation can never fail, it is safe to allow general_operand constraints
> on the QImode shift
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
at CFG construction time and the middle-end will place
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98782
--- Comment #6 from Jan Hubicka ---
I am sorry for getting back to this again late. This stage1 we spent some time
with Martin improving the ipa-cp profile updating and looked again into the
realism of the profile. Also recently the codegen has
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103455
--- Comment #3 from Stephan Hartmann ---
Scratch comment 2, copied wrong one:
template
struct raw_ptr {
T* operator->() const;
operator T*() const;
template
explicit operator U*() const;
};
struct bar {};
struct foo {
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103455
--- Comment #2 from Stephan Hartmann ---
Handwritten reduced testcase:
template
struct raw_ptr {
T* operator->() const;
template
explicit operator U*() const;
};
struct bar {
static void func();
};
struct foo {
typedef
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=26163
Bug 26163 depends on bug 103227, which changed state.
Bug 103227 Summary: [12 Regression] 58% exchange2 regression with -Ofast
-march=native on zen3 since r12-5223-gecdf414bd89e6ba251f6b3f494407139b4dbae0e
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103227
Jan Hubicka changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
Hi,
this patch adds simple code to dump and compare frequencies of basic blocks
read from the profile feedback and frequencies guessed statically.
It dumps basic blocks in the order of decreasing frequencies from feedback
along with guessed frequencies and histograms.
It makes it to possible spot
On 11/25/2021 6:23 AM, Richard Biener via Gcc-patches wrote:
We have quite a number of "default" returns that cannot be reached.
One is particularly interesting since it says (see patch below):
default:
gcc_unreachable ();
}
/* We can get here with --disable-checking.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101540
Andrew Pinski changed:
What|Removed |Added
URL||https://gcc.gnu.org/piperma
From: Andrew Pinski
This just adds a simplification to simplify_vector_constructor for
vector of 1 element to be VCE which should reduce memory usage in
the compiler and maybe allow for some more optimizations.
OK? Bootstrapped and tested on x86_64-linux-gnu with no regressions.
PR
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103455
Andrew Pinski changed:
What|Removed |Added
Known to fail||8.2.0
Keywords|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103455
Andrew Pinski changed:
What|Removed |Added
Summary|internal compiler error: in |[9/10/11/12 Regression]
Hi Rasmus,
(making progress but not quite there on the stdint business)
> On 1 Nov 2021, at 10:34, Rasmus Villemoes wrote:
>
> Since commit 78e49fb1bc (Introduce vxworks specific crtstuff support),
> the generic crtbegin.o/crtend.o have been unnecessary to build. So
> remove them from
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103261
anlauf at gcc dot gnu.org changed:
What|Removed |Added
CC||anlauf at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103456
Martin Liška changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Priority|P3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103456
Bug ID: 103456
Summary: [12 Regression] gcc/gcc.c:9502:8: runtime error: load
of address 0x009f5037 with insufficient space for
an object of type 'const char' since
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63691
John David Anglin changed:
What|Removed |Added
Status|REOPENED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103455
Bug ID: 103455
Summary: internal compiler error: in dependent_type_p, at
cp/pt.c:27057
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
This patch builds on the recent improvements to TImode rotations (and
Jakub's fixes to shldq/shrdq patterns). Now that expanding a TImode
rotation can never fail, it is safe to allow general_operand constraints
on the QImode shift amounts in rotlv1ti3 and rotrv1ti3 patterns.
I've also made an
This patch addresses PR target/100711 by introducing define_split
patterns so that not/broadcast/pand may be simplified (by combine)
to broadcast/pandn. This introduces two splitters one for optimizing
pandn on TARGET_SSE for V4SI and V2DI, and another for vpandn on
TARGET_AVX2 for V16QI, V8HI,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102609
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Ever confirmed|0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103448
--- Comment #10 from Janez Zemva ---
The code worked for ((...), (...), ...), but not for ((...)), I did not
understand how a tuple not containing another tuple could possibly be
constructed. On the other hand, I already found a workaround and
On Sun, Nov 28, 2021 at 4:11 PM Jan Hubicka wrote:
>
> > Hi,
> > In function ref_maybe_used_by_call_p_1, there is below code snippet
> > /* The following builtins do not read from memory. */
> > case BUILT_IN_FREE:
> > ...
> >return false;
> >
> > I am
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101540
Andrew Pinski changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned
On 11/25/21 14:59, Martin Liška wrote:
Fixes:
==129444==ERROR: AddressSanitizer: global-buffer-overflow on address
0x0666ca5c at pc 0x00ef094b bp 0x7fff8180 sp 0x7fff8178
READ of size 4 at 0x0666ca5c thread T0
#0 0xef094a in parse_optimize_options
4
# of expected failures 861
# of unresolved testcases 2
# of unsupported tests 2235
/home/xry111/gcc-test/gcc-12-larch-20211128/build/gcc/xgcc version 12.0.0
20211127 (experimental) (GCC)
=== gfortran tests ===
Running target unix
FAIL: gfortran.dg/bind_
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103454
Bug ID: 103454
Summary: -finline-functions-called-once is both compile-time
and runtime loss at average for spec2006, spec2017 and
tramp3d
Product: gcc
Version:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103444
--- Comment #3 from Andrew Pinski ---
https://groups.google.com/g/bsdmailinglist/c/PnRU5wlAAWw/m/o1DiaXuWAQAJ?pli=1
But PR 82635 has been fixed for a while now.
Otherwise maybe it is the stack size problem as mentioned in that freebsd bug.
> Hi,
> In function ref_maybe_used_by_call_p_1, there is below code snippet
> /* The following builtins do not read from memory. */
> case BUILT_IN_FREE:
> ...
>return false;
>
> I am confused because free function does read from (and even write to)
>
101 - 132 of 132 matches
Mail list logo
