From: xuli
Computation of `vsadd`, `vsaddu`, `vssub`, and `vssubu` do not need the
rounding mode, therefore the intrinsics of these instructions do not have
the parameter for rounding mode control.
gcc/ChangeLog:
* config/riscv/riscv-vector-builtins-bases.cc: remove rounding mode of
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110835
--- Comment #5 from Andrew Pinski ---
(In reply to Andrew Pinski from comment #3)
> (In reply to Andrew Pinski from comment #2)
> > Which might mean it is an issue in LLVM too ...
>
> Yes the same runtime regression shows up between clang 15
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110835
Andrew Pinski changed:
What|Removed |Added
Summary|-fsanitize=address causes |[13/14 Regression]
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110835
--- Comment #3 from Andrew Pinski ---
(In reply to Andrew Pinski from comment #2)
> Which might mean it is an issue in LLVM too ...
Yes the same runtime regression shows up between clang 15 and clang 16. This
should reported upstream to them
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110835
Andrew Pinski changed:
What|Removed |Added
CC||dodji at gcc dot gnu.org,
On Thu, 2023-07-27 at 15:11 +0200, Georg-Johann Lay wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the
> content is safe
>
> Am 17.07.23 um 13:33 schrieb SenthilKumar.Selvaraj--- via Gcc:
> > Hi,
> >
> >The avr target has a bunch of patterns that directly
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110835
--- Comment #1 from Ed Catmur ---
Motivation is
https://github.com/boostorg/exception/blob/b039b4ea18ef752d0c1684b3f715ce493b778060/include/boost/exception/detail/exception_ptr.hpp#L550
; the half-reduced code is:
#include
struct S {};
int
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110835
Bug ID: 110835
Summary: -fsanitize=address causes slowdown from
std::rethrow_exception not called
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity:
This patch uses _GLIBCXX_HAS_BUILTIN_TRAIT macro instead of
__has_builtin in the type_traits header. This macro supports to toggle
the use of built-in traits in the type_traits header through
_GLIBCXX_NO_BUILTIN_TRAITS macro, without needing to modify the
source code.
libstdc++-v3/ChangeLog:
This patch defines _GLIBCXX_HAS_BUILTIN_TRAIT macro, which will be used
as a flag to toggle the use of built-in traits in the type_traits header
through _GLIBCXX_NO_BUILTIN_TRAITS macro, without needing to modify the
source code.
libstdc++-v3/ChangeLog:
* include/bits/c++config
QR_001_July_23.xls
Description: MS-Excel spreadsheet
Sorry for not consider rv32 config.
The fix is OK. If convenient, please commit it.
On 2023/7/28 4:46, Patrick O'Neill wrote:
> The newly added testcase fails on rv32 targets with this message:
> FAIL: gcc.target/riscv/rvv/autovec/madd-split2-1.c -O3 -ftree-vectorize (test
> for excess errors)
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110788
--- Comment #6 from Hongtao.liu ---
Fixed in trunk.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108121
Gaius Mulley changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
On Thu, Jul 27, 2023 at 7:11 PM chuanqi.xcq via Gcc wrote:
>
> Hi,
> We're discussing to implement `-fno-coroutines` in clang so that we can
> disable the coroutine feature with C++ standard higher than 20.
> A full discussion can be found here: https://reviews.llvm.org/D156247. A
> major
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108121
--- Comment #11 from CVS Commits ---
The releases/gcc-13 branch has been updated by Gaius Mulley
:
https://gcc.gnu.org/g:50fc6ce0cb8edf927ae6117a5484e4d8d52e393e
commit r13-7619-g50fc6ce0cb8edf927ae6117a5484e4d8d52e393e
Author: Gaius Mulley
Hi,
We're discussing to implement `-fno-coroutines` in clang so that we can
disable the coroutine feature with C++ standard higher than 20.
A full discussion can be found here: https://reviews.llvm.org/D156247. A major
motivation for us to do this is to keep consistency with GCC.
However, we
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110788
--- Comment #5 from CVS Commits ---
The master branch has been updated by hongtao Liu :
https://gcc.gnu.org/g:54e54f77c1012ab53126314181c51eaee146ad5d
commit r14-2833-g54e54f77c1012ab53126314181c51eaee146ad5d
Author: liuhongt
Date: Thu Jul
On 7/27/23 18:59, Lewis Hyatt wrote:
In order to support processing #pragma in preprocess-only mode (-E or
-save-temps for gcc/g++), we need a way to obtain the #pragma tokens from
libcpp. In full compilation modes, this is accomplished by calling
pragma_lex (), which is a symbol that must be
From: Pan Li
Update in PATCH v8:
1. Emit non-abnormal backup insn to edge.
2. Fix _after return when call.
3. Refine some run tests.
4. Cleanup code.
Original commit logs:
In basic dynamic rounding mode, we simply ignore call instructions and
we would like to take care of call in this PATCH.
On 7/23/23 20:26, Ben Boeckel wrote:
On Fri, Jul 21, 2023 at 16:23:07 -0400, Nathan Sidwell wrote:
It occurs to me that the model I am envisioning is similar to CMake's object
libraries. Object libraries are a convenient name for a bunch of object files.
IIUC they're linked by naming the
On 7/23/23 20:26, Ben Boeckel wrote:
On Fri, Jul 21, 2023 at 16:23:07 -0400, Nathan Sidwell wrote:
It occurs to me that the model I am envisioning is similar to CMake's object
libraries. Object libraries are a convenient name for a bunch of object files.
IIUC they're linked by naming the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109986
--- Comment #5 from Ivan Sorokin ---
(In reply to CVS Commits from comment #4)
> commit r14-2751-g2a3556376c69a1fb588dcf25225950575e42784f
> Author: Drew Ross
> Co-authored-by: Jakub Jelinek
Thank you!
In order to support processing #pragma in preprocess-only mode (-E or
-save-temps for gcc/g++), we need a way to obtain the #pragma tokens from
libcpp. In full compilation modes, this is accomplished by calling
pragma_lex (), which is a symbol that must be exported by the frontend, and
which is
On 7/27/23 15:27, Jose E. Marchesi wrote:
>
> Hi David.
> Thanks for the patch.
>
>> BPF ISA V4 introduces sign-extending move and load operations. This
>> patch makes the BPF backend generate those instructions, when enabled
>> and useful.
>>
>> A new option, -m[no-]smov gates generation of
Snapshot gcc-11-20230727 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/11-20230727/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 11 git branch
with the following options: git://gcc.gnu.org/git/gcc.git branch
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110782
--- Comment #1 from CVS Commits ---
The master branch has been updated by David Faust :
https://gcc.gnu.org/g:14dab1a1bcc3f0315e33d166df06520fba409c9b
commit r14-2831-g14dab1a1bcc3f0315e33d166df06520fba409c9b
Author: David Faust
Date: Thu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110784
--- Comment #1 from CVS Commits ---
The master branch has been updated by David Faust :
https://gcc.gnu.org/g:14dab1a1bcc3f0315e33d166df06520fba409c9b
commit r14-2831-g14dab1a1bcc3f0315e33d166df06520fba409c9b
Author: David Faust
Date: Thu
On Thu, 2023-07-27 at 18:13 -0400, Eric Feng wrote:
> Hi Dave,
>
> Thanks for the comments!
>
> [...]
> > Do you have any DejaGnu tests for this functionality? For example,
> > given PyList_New
> > https://docs.python.org/3/c-api/list.html#c.PyList_New
> > there could be a test like:
> >
> >
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110834
Bug ID: 110834
Summary: Incorrect format-nonliteral warning when wrapping a
printf-family function using __builtin_va_arg_pack
Product: gcc
Version: 13.2.1
Status:
Hi David.
Thanks for the patch.
> BPF ISA V4 introduces sign-extending move and load operations. This
> patch makes the BPF backend generate those instructions, when enabled
> and useful.
>
> A new option, -m[no-]smov gates generation of these instructions, and is
> enabled by default for
Hi David, thanks for the patch.
OK.
> This patch makes some minor cleanups to eBPF options documented in
> invoke.texi:
> - Delete some vestigal docs for removed -mkernel option
> - Add -mbswap and -msdiv to the option summary
> - Note the negative versions of several options
> - Note that
On Tue, 2023-04-11 at 08:43 +, Richard Biener wrote:
> On Tue, 4 Apr 2023, David Malcolm wrote:
>
> > Richi, Jakub: I can probably self-approve this, but it's
> > technically a
> > new feature. OK if I push this to trunk in stage 4? I believe
> > it's
> > low risk, and is very useful for
Hi Dave,
Thanks for the comments!
[...]
> Do you have any DejaGnu tests for this functionality? For example,
> given PyList_New
> https://docs.python.org/3/c-api/list.html#c.PyList_New
> there could be a test like:
>
> /* { dg-require-effective-target python_h } */
>
> #define
BPF ISA V4 introduces sign-extending move and load operations. This
patch makes the BPF backend generate those instructions, when enabled
and useful.
A new option, -m[no-]smov gates generation of these instructions, and is
enabled by default for -mcpu=v4 and above. Tests for the new
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108835
--- Comment #9 from Gaius Mulley ---
This looks fixed from the commit trail - can this PR be closed now?
This patch makes some minor cleanups to eBPF options documented in
invoke.texi:
- Delete some vestigal docs for removed -mkernel option
- Add -mbswap and -msdiv to the option summary
- Note the negative versions of several options
- Note that -mcpu=v4 also enables -msdiv.
gcc/
*
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106293
--- Comment #16 from Jan Hubicka ---
It is really hard to make loop splitting to do something.
It does not like canonicalized invariant variables since loop exit condition
should not be NE_EXPR and it does not like when VRP turns LT/GT into NE.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110824
--- Comment #5 from Andrew Pinski ---
(In reply to Denis Yaroshevskiy from comment #4)
> Appreciate it.
>
> I'm still going to support gcc11 for the forseable future. Is there some
> easy way you see I can confirm that this is this issue?
> So
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109586
--- Comment #5 from CVS Commits ---
The releases/gcc-13 branch has been updated by Gaius Mulley
:
https://gcc.gnu.org/g:2286745b12070320c8dcc5c75d76dd184cb7645e
commit r13-7616-g2286745b12070320c8dcc5c75d76dd184cb7645e
Author: Gaius Mulley
Hi Tobias!
On 2023-07-25T23:45:54+0200, Tobias Burnus wrote:
> The attached patch calls CUDA's cuMemcopy2D and cuMemcpy3D
> for omp_target_memcpy_rect[,_async} for dim=2/dim=3. This should
> speed up the data transfer for noncontiguous data.
ACK, thanks.
> While being there, I ended up adding
The newly added testcase fails on rv32 targets with this message:
FAIL: gcc.target/riscv/rvv/autovec/madd-split2-1.c -O3 -ftree-vectorize (test
for excess errors)
verbose log:
compiler exited with status 1
output is:
cc1: error: ABI requires '-march=rv32'
Something like this appears to fix the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110817
--- Comment #9 from Andrew Pinski ---
Here is a reduced testcase that does not need -mno-sse or any other option but
fails everywhere:
```
typedef unsigned __attribute__((__vector_size__ (1*sizeof(unsigned V;
V v;
unsigned char c;
int
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110825
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Status|NEW |ASSIGNED
Dear all,
when passing a character actual argument to an assumed-type dummy
(TYPE(*)), we should not pass the character length for that argument,
as otherwise other hidden arguments that are passed as part of the
gfortran ABI will not be interpreted correctly. This is in line
with the current
On Linux/x86_64,
7931a1de9ec87b996d51d3d60786f5c81f63919f is the first bad commit
commit 7931a1de9ec87b996d51d3d60786f5c81f63919f
Author: Jonathan Wakely
Date: Wed Jul 26 14:09:24 2023 +0100
libstdc++: Avoid bogus overflow warnings in std::vector [PR110807]
caused
FAIL:
I think there should be tests for _Atomic _BitInt types. Hopefully atomic
compound assignment just works via the logic for compare-and-exchange
loops, but does e.g. atomic_fetch_add work with _Atomic _BitInt types?
--
Joseph S. Myers
jos...@codesourcery.com
> Am 27.07.2023 um 19:12 schrieb Roger Sayle :
>
>
> Hi Richard,
>
> You're 100% right. It’s possible to significantly clean-up this code,
> replacing
> the body of the conditional with a call to force_reg and simplifying the
> conditions
> under which it is called. These improvements
Excerpts from Andreas Schwab via Gcc-patches's message of Juli 24, 2023 11:15
am:
> Ping?
>
OK from me.
Thanks,
Iain.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110831
--- Comment #1 from seurer at gcc dot gnu.org ---
Also this one:
FAIL: gcc.dg/strcmpopt_5.c (internal compiler error: in to_gcov_type, at
profile-count.h:831)
FAIL: gcc.dg/strcmpopt_5.c (test for excess errors)
> The pseudo-C output templates for these instructions were incorrectly
> using operand 1 rather than operand 2 on the RHS, which led to some
> very incorrect assembly generation with -masm=pseudoc.
>
> Tested on bpf-unknown-none.
> OK?
OK. Thanks for spotting and fixing this!
>
> gcc/
>
>
On Thu, 27 Jul 2023, Jakub Jelinek via Gcc-patches wrote:
> - _BitInt(N) bit-fields aren't supported yet (the patch rejects them); I'd
> like
> to enable those incrementally, but don't really see details on how such
> bit-fields should be laid-out in memory nor passed inside of function
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110833
Bug ID: 110833
Summary: gamess regression on Ice Lake with -Ofast
-march=native between g:1c6231c05bdccab3 (2023-07-21
03:06) and g:bbc1a102735c72e3 (2023-07-23 04:55)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110832
--- Comment #2 from Jan Hubicka ---
I tested that the profile change makes no difference.
Hi,
as discussed with Richard, we want store to be likely in
optimize_mask_stores.
Bootstrapped/regtested x86_64-linux, comitted.
gcc/ChangeLog:
* tree-vect-loop.cc (optimize_mask_stores): Make store
likely.
diff --git a/gcc/tree-vect-loop.cc b/gcc/tree-vect-loop.cc
index
This patch fixes profile update after RTL unroll, that is now done same way as
in tree one. We still produce (slightly) corrupted profile for multiple exit
loops I can try to fix incrementally.
I also updated testcases to look for profile mismatches so they do not creep
back in again.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110587
Roger Sayle changed:
What|Removed |Added
Assignee|roger at nextmovesoftware dot com |unassigned at gcc dot
gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110701
--- Comment #7 from Roger Sayle ---
Patch proposed here:
https://gcc.gnu.org/pipermail/gcc-patches/2023-July/625532.html
The pseudo-C output templates for these instructions were incorrectly
using operand 1 rather than operand 2 on the RHS, which led to some
very incorrect assembly generation with -masm=pseudoc.
Tested on bpf-unknown-none.
OK?
gcc/
* config/bpf/bpf.md (add3): Use %w2 instead of %w1
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106293
--- Comment #15 from Jan Hubicka ---
if (bb_loop_depth (best_bb) == bb_loop_depth (early_bb)
/* If result of comparsion is unknown, prefer EARLY_BB.
Thus use !(...>=..) rather than (...<...) */
- && !(best_bb->count *
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85944
Andrew Pinski changed:
What|Removed |Added
CC||gccbugbjorn at fahller dot se
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55004
Bug 55004 depends on bug 110828, which changed state.
Bug 110828 Summary: union constexpr dtor not constexpr when used in member array
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110828
What|Removed |Added
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110828
Andrew Pinski changed:
What|Removed |Added
Resolution|--- |DUPLICATE
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110755
--- Comment #14 from CVS Commits ---
The releases/gcc-13 branch has been updated by Jakub Jelinek
:
https://gcc.gnu.org/g:e684084a5fa9edaedb1a14e118b966a60e3449b9
commit r13-7615-ge684084a5fa9edaedb1a14e118b966a60e3449b9
Author: Jakub Jelinek
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110827
--- Comment #4 from Michael Duggan ---
I should be more explicit. The `std::cout` line in the example is just a
placeholder for "does some work here," and this example is specifically the
simplest version of a coroutine I could come up with
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110832
--- Comment #1 from Jan Hubicka ---
This time it seems that there is only one profile change:
commit 645c67f80c6258c1f54ec567f604008adbdb8a04
Author: Jan Hubicka
Date: Wed Jul 26 08:59:23 2023 +0200
Fix profile_count::to_sreal_scale
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110832
Bug ID: 110832
Summary: 14% capacita -O2 regression between g:9fdbd7d6fa5e0a76
(2023-07-26 01:45) and g:ca912a39cccdd990 (2023-07-27
03:44) on zen3 and core
Product: gcc
On Thu, Jul 27, 2023 at 07:15:28PM +0200, Jakub Jelinek via Gcc-patches wrote:
> testcases, I've been using
> https://defuse.ca/big-number-calculator.htm
> tool, a randombitint tool I wrote (will post as a reply to this) plus
> LLVM trunk on godbolt and the WIP GCC support checking if both
Hi!
This patch adds the C FE support, c-family support, small libcpp change
so that 123wb and 42uwb suffixes are handled plus glimits.h change
to define BITINT_MAXWIDTH macro.
The previous two patches really do nothing without this, which enables
all the support.
2023-07-27 Jakub Jelinek
Hi!
This patch adds the library helpers for multiplication, division + modulo
and casts from and to floating point.
As described in the intro, the first step is try to reduce further the
passed in precision by skipping over most significant limbs with just zeros
or sign bit copies. For
Hi Richard,
You're 100% right. It’s possible to significantly clean-up this code, replacing
the body of the conditional with a call to force_reg and simplifying the
conditions
under which it is called. These improvements are implemented in the patch
below, which has been tested on
[PATCH 0/5] GCC _BitInt support [PR102989]
The following patch series introduces support for C23 bit-precise integer
types. In short, they are similar to other integral types in many ways,
just aren't subject for integral promotions if smaller than int and they can
have even much wider
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110831
Bug ID: 110831
Summary: [14 regression] gcc.dg/stack-check-3.c ICEs after
r14-2822-g499b8079a6419b
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity:
Yet another omission, the flag was not properly set for deeply buried
'omp teams' as I stopped too early when walking up the stack.
Now fixed by commit r14-2826-g081e25d3cfd86c
* * *
This was found when 'repairing' the feature on the OG13
(devel/omp/gcc-13) branch for metadirectives, cf. the
Hi,
I trust this email finds you well.
Our Organization hiring the best and the brightest talent in the industry. We
hire individuals with a strong sense of pride in their performance, team
spirit, and a desire to excel. To provide our clients with Professional,
Quality and value added
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110828
--- Comment #2 from Björn Fahller ---
If I write it in the same way in a function, it compiles.
consteval auto f()
{
return S{}.f();
}
constexpr auto b = f();
However, if I break it into a constexpr object S s; and return s.f(), it does
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71065
--- Comment #8 from CVS Commits ---
The master branch has been updated by Tobias Burnus :
https://gcc.gnu.org/g:081e25d3cfd86c4094999ded0bbe99b91762013c
commit r14-2826-g081e25d3cfd86c4094999ded0bbe99b91762013c
Author: Tobias Burnus
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110725
--- Comment #9 from CVS Commits ---
The master branch has been updated by Tobias Burnus :
https://gcc.gnu.org/g:081e25d3cfd86c4094999ded0bbe99b91762013c
commit r14-2826-g081e25d3cfd86c4094999ded0bbe99b91762013c
Author: Tobias Burnus
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110781
Jose E. Marchesi changed:
What|Removed |Added
Resolution|--- |MOVED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102989
Jakub Jelinek changed:
What|Removed |Added
Attachment #55642|0 |1
is obsolete|
Tested x86_64-linux. Pushed to trunk. Backport to gcc-13 to follow.
-- >8 --
A decimal point was being added to the end of the string for {:#.0}
because the __expc character was not being set, for the _Pres_none
presentation type, so __s.find(__expc) didn't the 'e' in "1e+01" and so
we created
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108046
Jonathan Wakely changed:
What|Removed |Added
Last reconfirmed|2022-12-10 00:00:00 |2023-07-27
--- Comment #4 from
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108046
--- Comment #3 from CVS Commits ---
The master branch has been updated by Jonathan Wakely :
https://gcc.gnu.org/g:50bc490c090cc95175e6068ed7438788d7fd7040
commit r14-2825-g50bc490c090cc95175e6068ed7438788d7fd7040
Author: Jonathan Wakely
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107172
--- Comment #52 from Shaohua Li ---
*** Bug 107257 has been marked as a duplicate of this bug. ***
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107257
Shaohua Li changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|WAITING
On 7/27/23 02:43, Xiao Zeng wrote:
2. According to your opinions, I have modified the code, but out of caution
for upstream, I conducted a complete regression tests on patch V2, which took
some time. I was unable to reply to emails and upload patch V2 in a timely
manner.
Sorry to have
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110809
--- Comment #9 from CVS Commits ---
The releases/gcc-13 branch has been updated by Patrick Palka
:
https://gcc.gnu.org/g:8e811edea309b2097e23cde48ee6fb6467a9094d
commit r13-7614-g8e811edea309b2097e23cde48ee6fb6467a9094d
Author: Patrick Palka
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110828
Patrick Palka changed:
What|Removed |Added
CC||ppalka at gcc dot gnu.org
--- Comment
Hi,
This patch fixes profile update in tree_transform_and_unroll_loop which is used
by predictive comming. I stared by attempt to fix
gcc.dg/tree-ssa/update-unroll-1.c I xfailed last week, but it turned to be
harder job.
Unrolling was never fixed for changes in duplicate_loop_body_to_header_edge
Hi,
this fixes two bugs in tree-ssa-loop-im.cc. First is that cap probability is
not
reliable, but it is constructed with adjusted quality. Second is that sometimes
the conditional has wrong joiner BB count. This is visible on
testsuite/gcc.dg/pr102385.c however the testcase triggers another
Hi,
profile_count::apply_probability misses check for uninitialized
probability which leads to completely random results on applying
uninitialized probability to initialized scale. This can make
difference when i.e. inlining -fno-guess-branch-probability function to
-fguess-branch-probability
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91838
Richard Biener changed:
What|Removed |Added
Resolution|--- |FIXED
Status|REOPENED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110827
--- Comment #3 from Michael Duggan ---
(In reply to Richard Biener from comment #1)
> I'm seeing all code properly instrumented. The coverage I see is
>
> -:1:#include
> -:2:#include
> -:3:
> -:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91838
--- Comment #19 from CVS Commits ---
The master branch has been updated by Richard Biener :
https://gcc.gnu.org/g:d1c072a1c3411a6fe29900750b38210af8451eeb
commit r14-2821-gd1c072a1c3411a6fe29900750b38210af8451eeb
Author: Richard Biener
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110788
--- Comment #4 from Hongtao.liu ---
> kmovw %edx, %k0
> vpbroadcastmw2d %k0, %xmm1
>
> instead of
>
> vpbroadcastw%edx, %xmm1
>
It's not vpbroadcastw, it's
movzwl %dx, %ecx
vpbroadcastd%ecx, %xmm0.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92335
Richard Biener changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |rguenth at gcc dot
gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64031
Richard Biener changed:
What|Removed |Added
Target Milestone|--- |14.0
Status|NEW
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53947
Bug 53947 depends on bug 64031, which changed state.
Bug 64031 Summary: (un-)conditional execution state is not preserved by PRE/sink
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64031
What|Removed |Added
Hey,
On Thu, 27 Jul 2023, Thomas Koenig via Gcc wrote:
> Intel recommends to have the new registers as caller-saved for
> compatibility with current calling conventions. If I understand this
> correctly, this is required for exception unwinding, but not if the
> function called is
Prevent rtl optimization of vec_duplicate + zero_extend to
vpbroadcastm since there could be an extra kmov after RA.
Bootstrapped and regtested on x86_64-pc-linux-gnu{-m32,}
Ready to push to trunk.
gcc/ChangeLog:
PR target/110788
* config/i386/sse.md (avx512cd_maskb_vec_dup):
1 - 100 of 306 matches
Mail list logo
