Hi folks,
some more suggestions for corrections in the onlinedocs:
https://gcc.gnu.org/onlinedocs/gcc-11.1.0/gfortran/GERROR.html#GERROR
RESULT "Shall of type CHARACTER and of default"
--> "Shall BE of ... default KIND."
Hi Philip,
On Mon, May 24, 2021 at 02:24:13PM +0100, Philip Herron wrote:
> As some of you might know, I have been working on GCC Rust over on
> GitHub https://github.com/Rust-GCC/gccrs. As the project is moving
> forward and enforcing GCC copyright assignments for contributors, I
> would like to
On 5/24/21 2:18 AM, Uecker, Martin wrote:
I wonder if we could get a nice short command-line option
for recommended safety/security related flags.
We have -Ox for optimization and -Wall for a useful set
of recommended warnings.
I am thinking about options such as
-ftrapv
It isn't exposed on my platform either. Looks like a bug in
perf_data_converter (i.e., quipper). Could you try adding #include
in
third_party/perf_data_converter/src/quipper/huge_page_deducer.cc and
see if it fixes the problem? If it works, I will need to file a bug
against perf_data_converter.
That fixed the error I saw before but the build still fails. The errors start
with
eugene@eugene-Virtual-Machine:~/autofdo1/build$ ninja
[2/217] Building CXX object
CMakeFiles/quipper_perf.dir/third_party/perf_data_converter/src/quipper/huge_page_deducer.cc.o
FAILED:
Thank you Wei. Looks like something is still missing. This time perf_data.pb.h
is not found. I'm getting the error below (on Ubuntu 18.04 with cmake 3.12.1):
eugene@eugene-Virtual-Machine:~/autofdo1/build$ ninja
[1/241] Building CXX object CMakeFiles/dump_gcov_lib.dir/profile.cc.o
FAILED:
Sorry, I added dependency for create_gcov but missed it for dump_gcov.
Fixed it at
https://github.com/google/autofdo/commit/6ca36cdc30986f13583a3aef3e27746ca4fc5bf6
.
Thanks,
Wei.
On Mon, May 24, 2021 at 6:39 PM Eugene Rozenfeld <
eugene.rozenf...@microsoft.com> wrote:
> Thank you Wei. Looks
PING^1
On 1/14/21 10:02 AM, Martin Liška wrote:
On 1/13/21 6:00 PM, Joseph Myers wrote:
I'm fine with having it set up with a public repository.
Ok, can you please do it Joseph?
If you have a
public (bare) repository that would of course need to have its own hooks
to update the (non-bare)
I wonder if we could get a nice short command-line option
for recommended safety/security related flags.
We have -Ox for optimization and -Wall for a useful set
of recommended warnings.
I am thinking about options such as
-ftrapv
-fsanitize=undefined -fsanitize-undefined-trap-on-error
On 5/21/21 2:35 PM, David Edelsohn wrote:
Please remember that not all targets support LTO so a fallback to a
non-partial-LTO build needs to be provided and automatically invoked
for those targets.
Sure, for now it's definitely going to be a opt-in, enabled by something like:
make
Hi everyone,
As some of you might know, I have been working on GCC Rust over on
GitHub https://github.com/Rust-GCC/gccrs. As the project is moving
forward and enforcing GCC copyright assignments for contributors, I
would like to create a branch on the GCC git repo to show the intention
to be
On 5/24/21 1:44 PM, Gejoe Daniel via Gcc wrote:
Adding gcc mailing list for the clarification.
Thank you team !
From: Gejoe Danielgej...@rediffmail.com
Sent: Mon, 24 May 2021 15:02:12
To: gcc-h...@gcc.gnu.orggcc-h...@gcc.gnu.org
Subject: Re: Regarding __gcov_dump and __gcov_reset usage
Hi
Hello,
On Sun, May 23 2021, Ankur Saini wrote:
> Hello,
>
>> On 18-May-2021, at 9:52 PM, Martin Jambor wrote:
>>
>> All accepted students which do not already have one must request a
>> copyright assignment[1] as soon as possible. Please email the
>> following information to ass...@gnu.org and
Adding gcc mailing list for the clarification.
Thank you team !
From: Gejoe Danielgej...@rediffmail.com
Sent: Mon, 24 May 2021 15:02:12
To: gcc-h...@gcc.gnu.orggcc-h...@gcc.gnu.org
Subject: Re: Regarding __gcov_dump and __gcov_reset usage
Hi team,
Any info/reply ?
Thanking you in advance,
On Mon, 24 May 2021, Philip Herron wrote:
> remote: error: hook declined to update refs/heads/gccrs
refs/heads/gccrs doesn't match the branch naming conventions as documented
at https://gcc.gnu.org/git.html (where you'd use refs/heads/devel/* for
shared development branches), so if you hadn't
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61238
Andrew Pinski changed:
What|Removed |Added
Status|WAITING |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84862
Andrew Pinski changed:
What|Removed |Added
Resolution|--- |INVALID
Status|WAITING
These tests rely on ADL for some functions, probably unintentionally.
The calls only work because the iterator wrappers derive from
std::iterator and so namespace std is an associated namespace.
libstdc++-v3/ChangeLog:
* testsuite/25_algorithms/inplace_merge/constrained.cc: Qualify
VARYING ranges are just normal ranges that span the entire domain. Such
ranges have had end-points for a few releases now, and the fact that the
legacy code was still treating all VR_VARYING the same was an oversight.
This patch fixes the oversight to match the multi-range behavior.
Tested on
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100537
--- Comment #17 from CVS Commits ---
The master branch has been updated by Ian Lance Taylor :
https://gcc.gnu.org/g:358832c46a378e5a0b8a2fa3c2739125e3e680c7
commit r12-1022-g358832c46a378e5a0b8a2fa3c2739125e3e680c7
Author: Ian Lance Taylor
On Sat, 22 May 2021, H.J. Lu via Gcc-patches wrote:
> 1. Update PUSH_ARGS to accept an argument. When the PUSH instruction
> usage is optional, pass the number of bytes to push to PUSH_ARGS so that
> the backend can decide if PUSH instructions should be generated.
> 2. Change x86 PUSH_ARGS to
Hi folks,
some more suggestions for corrections in the onlinedocs:
https://gcc.gnu.org/onlinedocs/gcc-11.1.0/gfortran/GERROR.html#GERROR
RESULT "Shall of type CHARACTER and of default"
--> "Shall BE of ... default KIND."
On Mon, May 24, 2021 at 12:37:30AM +0200, Bernhard Reutner-Fischer wrote:
> On 21 May 2021 22:56:09 CEST, Bill Schmidt via Gcc-patches
> wrote:
> >>> + char *buf = (char *) malloc (lastpos - pos + 2);
> >>> + memcpy (buf, [pos], lastpos - pos + 1);
> >>> + buf[lastpos - pos + 1] = '\0';
>
The attached patch introduces the get_no_warning(), set_no_warning(),
and copy_no_warning() APIs without making use of them in the rest of
GCC. They are in three files:
diagnostic-spec.{h,c}: Location-centric overloads.
warning-control.cc: Tree- and gimple*-centric overloads.
The
The attached patch replaces TREE_NO_WARNING, gimple_get_no_warning_p
and gimple_set_no_warning with the new APIs, get_no_warning,
set_no_warning, and copy_no_warning.
Add support for per-location warning groups.
gcc/ChangeLog:
* builtins.c (warn_string_no_nul): Replace uses of TREE_NO_WARNING,
The attached patch replaces the uses of TREE_NO_WARNING in libc11.
Add support for per-location warning groups.
libcc1/ChangeLog:
* libcp1plugin.cc (record_decl_address): Replace a direct use
of TREE_NO_WARNING with set_no_warning.
diff --git a/libcc1/libcp1plugin.cc b/libcc1/libcp1plugin.cc
In the testcase below, the initializer for C::b inside C's default
constructor is encoded as a TARGET_EXPR wrapping the CALL_EXPR f() in
C++17 mode. During massaging of this constexpr constructor,
build_target_expr_with_type called from bot_manip ends up trying to use
B's implicitly deleted copy
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100573
--- Comment #6 from Tobias Burnus ---
(In reply to Jakub Jelinek from comment #5)
> I think we want to fix both for-3.c and for-9.c similarly to
> r11-2571-g916c7a201a9a1dc94f2c056a773826a26d1daca9 i.e.
> #define DO_PRAGMA(x) _Pragma (#x)
>
One last addendum to this. I discovered that that needs a "sort"
in front of "keys %logicals_addsub" because otherwise you may get
the operators in different orders sometimes which leads to fusion.md
having the patterns in different orders which isn't helpful for
sane debugging. Segher and I
On 5/21/21 4:35 PM, Patrick Palka wrote:
Here, during ahead of time access checking for the private member
EnumeratorRange::end_reached_ in the hidden friend f, we're triggering
the the assert in enforce_access that verifies we're not trying to add a
dependent access check to
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100748
--- Comment #2 from seurer at gcc dot gnu.org ---
I do see it failing on at least one powerpc64 LE machine. PR97944 said it used
to fail randomly.
I've committed a patch to the Go frontend that fixes this problem.
Thanks for the analysis.
Ian
On Thu, May 20, 2021 at 1:59 AM guojiufu wrote:
>
> On 2021-05-18 14:58, Richard Biener wrote:
> > On Mon, 17 May 2021, Ian Lance Taylor wrote:
> >
> >> On Mon, May 17, 2021 at 1:17 AM Richard Biener
The attached patch replaces the uses of TREE_NO_WARNING in the C
front end.
Add support for per-location warning groups.
gcc/c/ChangeLog:
* c-decl.c (pop_scope): Replace direct uses of TREE_NO_WARNING with
get_no_warning, set_no_warning, and copy_no_warning.
(diagnose_mismatched_decls):
The attached patch replaces the uses of TREE_NO_WARNING in the C
family common subset of the C and C++ front ends.
Add support for per-location warning groups.
gcc/c-family/ChangeLog:
* c-common.c (c_wrap_maybe_const): Remove TREE_NO_WARNING.
(c_common_truthvalue_conversion): Replace direct
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100573
--- Comment #7 from Jakub Jelinek ---
Guess that is because the functions that have #pragma omp target teams
directive in it are marked declare target to.
So, either we'd need to play with macros etc. to make sure that those functions
aren't
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100748
Bug ID: 100748
Summary: [12 regression] 30_threads/jthread/95989.cc fails
after r12-843
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100537
Ian Lance Taylor changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
On Tue, May 18, 2021 at 5:31 AM Iain Buclaw wrote:
>
> Excerpts from Lewis Hyatt via Gcc-patches's message of January 29, 2021 4:46
> pm:
> > Q1: What is the input charset?
> > A1:
> >
> > libcpp: Whatever was passed to -finput-charset (note, for Fortran,
> > -finput-charset is not
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78889
Andrew Pinski changed:
What|Removed |Added
Resolution|--- |INVALID
Status|WAITING
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89694
Andrew Pinski changed:
What|Removed |Added
Resolution|--- |INVALID
Status|WAITING
On 5/21/21 5:39 AM, Aldy Hernandez via Gcc-patches wrote:
This patch converts the remaining users of get_range_info and
get_ptr_nonnull to the range_query API.
No effort was made to move passes away from VR_ANTI_RANGE, or any other
use of deprecated methods. This was a straight up conversion
On 5/21/21 4:35 PM, Patrick Palka wrote:
Here, in C++17 mode, convert_nontype_argument_function is rejecting
binding a non-noexcept function reference template parameter to a
noexcept function (encoded as the template argument '*(int (&) (int)) ').
The first roadblock to making this work is
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100085
--- Comment #8 from Segher Boessenkool ---
(In reply to luoxhu from comment #7)
> (In reply to Segher Boessenkool from comment #3)
> > The rotates in 6 and 7 are not merged, and neither are the vec_selects in
> > 8 and 9. Both should be pretty
The attached patch replaces the uses of TREE_NO_WARNING in the C++
front end. For the set/get_no_warning calls I tried to find the most
appropriate option to disable and query. In some cases there are
helpful comments nearby that made this easy. In other cases it was
less straightforward, and
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90217
Andrew Pinski changed:
What|Removed |Added
Resolution|--- |FIXED
Target Milestone|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100479
--- Comment #1 from CVS Commits ---
The master branch has been updated by Patrick Palka :
https://gcc.gnu.org/g:46ed811bcb4b86a81ef3d78ea8cfffc6cd043144
commit r12-1018-g46ed811bcb4b86a81ef3d78ea8cfffc6cd043144
Author: Patrick Palka
Date:
On 5/24/21 12:46 PM, Martin Sebor wrote:
Instantiating a hash_map on a number of integer types including,
for example, int or unsigned int (such as location_t), or
HOST_WIDE_INT, and using it with the garbage collector causes many
cryptic compilation errors due to incomplete support for such
The attached patch replaces the uses of TREE_NO_WARNING in
the Objective-C front end.
Add support for per-location warning groups.
gcc/objc/ChangeLog:
* objc-act.c (objc_maybe_build_modify_expr): Replace direct uses
of TREE_NO_WARNING with get_no_warning, and set_no_warning.
The attached patch replaces the uses of TREE_NO_WARNING in the Fortran
front end.
I don't know the Fortran front end and I made no effort to try to find
the right warning options in the calls to set/get_no_warning.
Add support for per-location warning groups.
gcc/fortran/ChangeLog:
*
The attached patch replaces the uses of TREE_NO_WARNING in the LTO
front end. The streaming support doesn't extend to multiple bits yet.
I plan to do that in a follow-up change.
Add support for per-location warning groups.
gcc/lto/ChangeLog:
* gimple-streamer-out.c (output_gimple_stmt): Same.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100666
Jakub Jelinek changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81612
Andrew Pinski changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|WAITING
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79760
Andrew Pinski changed:
What|Removed |Added
CC||vctrex at mailfence dot com
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81955
Andrew Pinski changed:
What|Removed |Added
Ever confirmed|1 |0
Status|WAITING
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88360
Andrew Pinski changed:
What|Removed |Added
Resolution|--- |INVALID
Status|WAITING
On 5/21/21 5:39 AM, Aldy Hernandez via Gcc-patches wrote:
This patch provides a generic API for accessing global ranges. It is
meant to replace get_range_info() and get_ptr_nonnull() with one
common interface. It uses the same API as the ranger (class
range_query), so there will now be one API
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100747
Bug ID: 100747
Summary: Possibly Wrong Permissions in "liboffloadmic"
Product: gcc
Version: 11.1.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component:
On Fri, 21 May 2021, Martin Liška wrote:
> CPUs:
> aarch64, alpha, alpha64, amdgcn, arc, arceb, arm, avr, bfin, bpf, cr16, cris,
> csky, epiphany, fido, fr30, frv, ft32, h8300, hppa, hppa2.0, hppa64, i486,
> i686, ia64, iq2000, lm32, m32c, m32r, m32rle, m68k, mcore, microblaze, mips,
> mips64,
This patch to the Go frontend marks global variables whose address is
taken. To implement this, change the backend to use flag bits for
variables. This fixes GCC PR 100537. Bootstrapped and ran Go
testsuite on x86_64-pc-linux-gnu. Committed to mainline.
Ian
PR go/100537
*
Having just one bit control whether an expression or statement should
be allowed to trigger warnings has been a source of bug reports about
false negatives for years. PR 74765 has a representative test case
that shows how by setting the bit to avoid -Wparentheses the C++ front
end also ends up
The attached patch replaces the uses of TREE_NO_WARNING in the rl78
back end.
Add support for per-location warning groups.
gcc/ChangeLog:
* config/rl78/rl78.c (rl78_handle_naked_attribute): Replace a direct
use of TREE_NO_WARNING with set_no_warning.
diff --git a/gcc/config/rl78/rl78.c
Instantiating a hash_map on a number of integer types including,
for example, int or unsigned int (such as location_t), or
HOST_WIDE_INT, and using it with the garbage collector causes many
cryptic compilation errors due to incomplete support for such types
(the PR shows a few examples). I ran
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100749
Bug ID: 100749
Summary: [12 regression] gcc.dg/pch/valid-1.c fails after
r12-949
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Severity: normal
Please, get serious.
=> this topic is closed for me, so STOP CC''ing ME, it is not welcome.
On Sun, 23 May 2021 at 19:03, Mike Stump wrote:
> This isn't a patch to gcc, please stop posting non-technical content to
> this list. Please review what this list is for and the rules for this list
>
On 18/05/21 00:53 -0400, Patrick Palka via Libstdc++ wrote:
On Mon, 17 May 2021, Tim Song wrote:
On Mon, May 17, 2021 at 2:59 PM Patrick Palka wrote:
>
> + constexpr _CachedPosition&
> + operator=(_CachedPosition&& __other) noexcept
> + {
> + if
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95298
Patrick Palka changed:
What|Removed |Added
Last reconfirmed||2021-05-24
Known to fail|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100745
Nicolas F. changed:
What|Removed |Added
Attachment #50861|0 |1
is obsolete|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100745
--- Comment #1 from Nicolas F. ---
I'll attach a second version of profile.c, with the vector extension code
that's actually going to be used in mpv (some cleanup has been done).
Performance is unchanged. Some absolute numbers from gcc 11.1.0:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100746
--- Comment #1 from Marc Glisse ---
PR 80740 ?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100748
Jonathan Wakely changed:
What|Removed |Added
Last reconfirmed||2021-05-24
[PATCH 2/11] use xxx_no_warning APIs in Ada.
Add support for per-location warning groups.
gcc/ada/ChangeLog:
* gcc-interface/trans.c (Handled_Sequence_Of_Statements_to_gnu):
Replace TREE_NO_WARNING with set_no_warning.
(gnat_gimplify_expr): Same.
* gcc-interface/utils.c (gnat_pushdecl):
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84187
Andrew Pinski changed:
What|Removed |Added
Ever confirmed|1 |0
Status|WAITING
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100724
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Known to fail||10.3.1, 11.1.0, 12.0,
On 5/24/21 1:48 PM, Patrick Palka wrote:
In the testcase below, the initializer for C::b inside C's default
constructor is encoded as a TARGET_EXPR wrapping the CALL_EXPR f() in
C++17 mode. During massaging of this constexpr constructor,
build_target_expr_with_type called from bot_manip ends up
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=74762
Martin Sebor changed:
What|Removed |Added
Keywords||patch
Assignee|unassigned at
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=74765
Martin Sebor changed:
What|Removed |Added
Keywords||patch
--- Comment #7 from Martin Sebor
On 5/24/21 5:08 PM, David Malcolm wrote:
On Mon, 2021-05-24 at 16:02 -0600, Martin Sebor wrote:
Having just one bit control whether an expression or statement should
be allowed to trigger warnings has been a source of bug reports about
false negatives for years. PR 74765 has a representative
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100711
--- Comment #3 from Hongtao.liu ---
(In reply to Segher Boessenkool from comment #2)
> (In reply to Richard Biener from comment #1)
> > I suppose we're confused about the vec_duplicate. Would generally swapping
> > the duplicate and the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100750
Bug ID: 100750
Summary: new test case gcc.target/powerpc/rop-5.c fails on BE
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
On Mon, 2021-05-24 at 16:16 -0600, Martin Sebor via Gcc-patches wrote:
> The attached patch replaces TREE_NO_WARNING, gimple_get_no_warning_p
> and gimple_set_no_warning with the new APIs, get_no_warning,
> set_no_warning, and copy_no_warning.
Might be worth splitting this out into
(a) the
On 5/24/21 5:08 PM, David Malcolm via Gcc-patches wrote:
On Mon, 2021-05-24 at 16:16 -0600, Martin Sebor via Gcc-patches wrote:
The attached patch replaces TREE_NO_WARNING, gimple_get_no_warning_p
and gimple_set_no_warning with the new APIs, get_no_warning,
set_no_warning, and copy_no_warning.
Hi Thomas,
I reproduced this issue manually and it turns out this is a special case.
Script takes input from https://gcc.gnu.org/pipermail/gcc-regression/ and
it matches the exact error message in the triaging process. This failure
reported on gcc regression
On Mon, 2021-05-24 at 16:02 -0600, Martin Sebor wrote:
> Having just one bit control whether an expression or statement should
> be allowed to trigger warnings has been a source of bug reports about
> false negatives for years. PR 74765 has a representative test case
> that shows how by setting
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100748
--- Comment #3 from Jonathan Wakely ---
I'd better disable it again until I have time to figure it out.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100310
--- Comment #2 from Hongtao.liu ---
w/o mask operands, v{,p}expand* are equal to mov instructions.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95782
--- Comment #1 from Evan Nemerson ---
This seems to also happen on s390x with -mzvector:
# s390x-linux-gnu-gcc-10 -march=z14 -mzvector -o test test.c
test.c:4:1: internal compiler error: in _cpp_pop_context, at
libcpp/macro.c:2644
4 |
Hi:
This patch is about to do transformation like below.
Bootstrapped and regtested on x86_64-linux-gnu{-m32,}.
Ok for trunk?
from
notl%edi
vpbroadcastd%edi, %xmm0
vpand %xmm1, %xmm0, %xmm0
to
vpbroadcastd%edi, %xmm0
vpandn %xmm1,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=22568
--- Comment #16 from Andrew Pinski ---
(In reply to Andrew Pinski from comment #15)
> The expr.c patch yes. The tree-ssa-phiopt.c patch, no. Tree-ssa-phiopt.c
> needs more code rework because of the new infrastructures so I have not
> gotten
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91540
--- Comment #3 from Andrew Pinski ---
Currently on the trunk we get:
andl%edi, %esi
movl$43, %eax
movzbl %sil, %esi
subl%esi, %eax
Which is close.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55869
Andrew Pinski changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|NEW
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97690
Andrew Pinski changed:
What|Removed |Added
CC||pawel_sikora at zoho dot com
---
Hi Andre,
on 2021/5/24 下午2:17, Andre Vieira (lists) via Gcc-patches wrote:
> Hi,
>
> When vectorizing with --param vect-partial-vector-usage=1 the vectorizer uses
> an unpredicated (all-true predicate for SVE) main loop and a predicated tail
> loop. The way this was implemented seems to mean
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100734
--- Comment #1 from Andrew Pinski ---
/* The character codes corresponding to all the access modes. */
static constexpr char mode_chars[5] = { '-', 'r', 'w', 'x', '^' };
Is this after building stage 1 or after building stage 2 ?
On 5/21/21 2:39 PM, Marco Elver wrote:
On Fri, May 21, 2021 at 10:50AM +0200, Martin Liška wrote:
On 5/20/21 12:55 PM, Marco Elver wrote:
I think this came up with other no_sanitize [1] based on what I had
written to you last year [2].
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100738
Andrew Pinski changed:
What|Removed |Added
Keywords||missed-optimization
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91383
Sandy Martel changed:
What|Removed |Added
CC||Sandy.Martel@lexisnexisrisk
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100736
Bug ID: 100736
Summary: ICE: unrecognizable insn
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Keywords: ice-on-valid-code
Severity: normal
Priority: P3
Hi,
When vectorizing with --param vect-partial-vector-usage=1 the vectorizer
uses an unpredicated (all-true predicate for SVE) main loop and a
predicated tail loop. The way this was implemented seems to mean it
re-uses the same vector-mode for both loops, which means the tail loop
isn't an
On 5/23/21 2:37 PM, Tobias Burnus wrote:
As there was some confusion regarding when the ChangeLog is generated,
I propose the attached wwwdocs patch. Comments?
I support the change. Moreover, I'm going to install the following
patch that adds a note about ChangeLog entries.
Martin
(Side
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97499
Andrew Pinski changed:
What|Removed |Added
Resolution|--- |INVALID
Status|WAITING
1 - 100 of 179 matches
Mail list logo
