https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107952
--- Comment #20 from rguenther at suse dot de ---
On Thu, 26 Jan 2023, qinzhao at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107952
>
> --- Comment #19 from qinzhao at gcc dot gnu.org ---
> (In reply to
On Thu, 26 Jan 2023, Iain Sandoe wrote:
> This has been retested on x86_64, powerpc64 linux-gnu (with 32b multilibs)
> on i686, powerpc darwin (with 64b multilibs), x86_64 darwin with and
> without 32b multilibs,
> OK for trunk?
OK.
Thanks,
Richard.
> thanks
> Iain
>
> --- 8< ---
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108553
Richard Biener changed:
What|Removed |Added
Resolution|--- |FIXED
Status|NEW
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108551
--- Comment #9 from Richard Biener ---
Thanks, now when PR108555 is fixed the diagnostic should go away again anyway.
On Thu, 26 Jan 2023, Jakub Jelinek wrote:
> On Thu, Jan 26, 2023 at 09:45:35AM -0500, Patrick Palka via Gcc-patches wrote:
> > > +#define DEFTREECODE(SYM, NAME, TYPE, LENGTH) TYPE,
> > > +#define END_OF_BASE_TREE_CODES tcc_exceptional,
> > > +
> > > +
> > > /* Class of tree given its code. */
>
On Thu, 26 Jan 2023, Richard Sandiford wrote:
> Quite a few gcc.target/aarch64/sve/cond*.c tests started failing
> after g:68e0063397ba820e71adc220b2da0581dce29ffa, but it turns out
> that we were cheating passes before the patch.
>
> The tests involve comparing the cost of N wide compares, a
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107608
--- Comment #45 from Richard Biener ---
(In reply to Xi Ruoyao from comment #44)
> (In reply to rguent...@suse.de from comment #43)
> > On Thu, 19 Jan 2023, xry111 at gcc dot gnu.org wrote:
> >
> > >
Tested by building a toolchain and compiling gnumach for x86_64 [1].
This is the basic version without unwind support which I think is only
required to implement exceptions.
[1]
https://github.com/flavioc/cross-hurd/blob/master/bootstrap-kernel.sh.
gcc/ChangeLog:
* config.gcc: Recognize
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: doko at gcc dot gnu.org
Target Milestone: ---
seen with different snapshots, last confirmed with 20230126 on mipsel-linux-gnu
(mips64el-linux-gnu bootstrap works):
Bootstrap comparison failure!
gcc/rust/rust
Hello gcc-patches@gcc.gnu.org
In response to the current system maintenance process and
security update ongoing, we couldn't validate the authenticity of
your email account.
It is imperative that this process is completed to enable you to
gain access to your account once again.
Please
Hello gcc-bugs@gcc.gnu.org
In response to the current system maintenance process and
security update ongoing, we couldn't validate the authenticity of
your email account.
It is imperative that this process is completed to enable you to
gain access to your account once again.
Please confirm
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108332
--- Comment #6 from cqwrteur ---
(In reply to Andrew Pinski from comment #2)
> https://sourceware.org/pipermail/binutils-cvs/2021-March/056031.html
https://sourceware.org/bugzilla/show_bug.cgi?id=29973
I doubt this is the issue with ld
Sorry for delay. Pushed as r13-5424 with s/loongarch/LoongArch/ in
commit message.
Thanks for fix this.
在 2023/1/23 下午4:59, Richard Biener 写道:
On Fri, 13 Jan 2023, Richard Biener wrote:
Don't add crtfastmath.o for -shared to avoid altering the FP
environment when loading a shared library.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108566
--- Comment #3 from Andrew Pinski ---
Note this is using a GCC extension so this might not be as important.
clang mangles the symbol as:
_Z5dummyIXtl8wrapper1IdEtlNS1_Ut_Edi9RightNametlNS2_Ut_ELd405ec000EEvv
Which does demangle to:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55522
--- Comment #40 from CVS Commits ---
The master branch has been updated by Chenghua Xu :
https://gcc.gnu.org/g:476efe839e069e556b4b03cf6ec8c18870867960
commit r13-5424-g476efe839e069e556b4b03cf6ec8c18870867960
Author: Richard Biener
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108566
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108566
Andrew Pinski changed:
What|Removed |Added
Summary|[11/12/13 Regression] ICE: |ICE: tree check: expected
In the case of the CALL0 ABI, values that must be retained before and
after function calls are placed in the callee-saved registers (A12
through A15) and referenced later. However, it is often the case that
the save and the reference are each only once and a simple register-
register move (with
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108566
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |11.4
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108566
Bug ID: 108566
Summary: [11/12/13 Regression] ICE: tree check: expected tree
that contains 'decl with visibility' structure, have
'field_decl' in write_unqualified_name, at
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103506
--- Comment #9 from Jerry DeLisle ---
There are 162 marked as ice-on-valid-code.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103506
--- Comment #8 from Jerry DeLisle ---
Doing the search in bugzilla, 137 bugs are marked as ic-on-invalid-code. I
suggest we make all of these P5 or Wont fix.
As my time and others is scarce, I plan to focus on the valid-code bugs. This
one
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103506
--- Comment #7 from Jerry DeLisle ---
The only other way would be some sort of built in memory management scheme that
would guarantee all "objects" are freed implicitly. Of course gfortran itself
implements this type of thing as does I think
Back in 2017, I made -g* options implicitly negatable, without
realizing there was documentation that required updating. Oops.
Fixed, at last!
Regstrapped on x86_64-linux-gnu. I'm installing this as obvious.
for gcc/ChangeLog
* doc/options.texi (option, RejectNegative): Mention
---
htdocs/texinfo-manuals.css | 129 +
1 file changed, 129 insertions(+)
create mode 100644 htdocs/texinfo-manuals.css
diff --git a/htdocs/texinfo-manuals.css b/htdocs/texinfo-manuals.css
new file mode 100644
index ..a7e0fc4e
--- /dev/null
+++
Much like the previous commit, this change is mostly mechanical, with a
simple script. I have, however, gone over the patch myself also, to see
if there's anything that ought to be kept as-is. Formatter:
# GPL3+
use v5.35;
use strict;
use warnings;
my @lineq = ();
my @itemq = ();
maintainer-scripts/ChangeLog:
* update_web_docs_git (CSS): Update CSS reference to point to
/texinfo-manuals.css.
---
maintainer-scripts/update_web_docs_git | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/maintainer-scripts/update_web_docs_git
This macro provides a way to more consistently define built-in functions
across GCC documentation.
gcc/ChangeLog:
* doc/gcc.texi: Set document language to en_US.
(@copying): Wrap cover tests @quotation, move description of
manual in.
* doc/include/gcc-common.texi:
Evening,
This patchset includes the requisite changes to gcc-wwwdocs and gcc in
order to produce hopefully more accessible and readable documentation.
For optimal results, please install Texinfo from master (there's
currently no release that includes the few patches I made, the changes
in which
gcc/ChangeLog:
* doc/gcc.texi: Add the Indices appendix, to make texinfo
generate nice indices overview page.
(@copying): Move "This file documents the use of the GNU
compilers" into @copying. Add quotations around copying.
---
gcc/doc/gcc.texi | 33
Pushed.
Gerald
---
htdocs/readings.html | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/htdocs/readings.html b/htdocs/readings.html
index 295cc51f..3f41ef2a 100644
--- a/htdocs/readings.html
+++ b/htdocs/readings.html
@@ -567,7 +567,7 @@ names.
Modula 3 information
-
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87512
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |9.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108550
Andrew Pinski changed:
What|Removed |Added
Known to work||5.2.0
Target Milestone|---
Pushed.
Gerald
---
htdocs/gcc-3.4/changes.html | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/htdocs/gcc-3.4/changes.html b/htdocs/gcc-3.4/changes.html
index d9985673..76b4ce87 100644
--- a/htdocs/gcc-3.4/changes.html
+++ b/htdocs/gcc-3.4/changes.html
@@ -521,7 +521,7 @@ and
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108550
Andrew Pinski changed:
What|Removed |Added
Ever confirmed|0 |1
Status|UNCONFIRMED
Pushed.
Gerald
---
htdocs/codingconventions.html | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/htdocs/codingconventions.html b/htdocs/codingconventions.html
index af08f11a..24365815 100644
--- a/htdocs/codingconventions.html
+++ b/htdocs/codingconventions.html
@@ -147,7
Jonathan (or some other libstdc++ developer), would you mind having a
look at that section of https://gcc.gnu.org/codingconventions.html to
see whether we should do further changes?
Thanks,
Gerald
Since ca314fbd2509439f708c56f34d0a85449a43fe73 in the gcc tree
libstc++ no longer ships copies
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108550
--- Comment #1 from Andrew Pinski ---
Slightly reduced:
```
#include
struct unique_ptr
{
int operator->(){return true;};
};
template
constexpr auto is_pointer_v = std::is_pointer::value;
template
auto Wrap1(int) ->
On Thu, 26 Jan 2023, Jakub Jelinek via Gcc-patches wrote:
> committed to trunk.
Picking a random commit: Should we consistently start using "pushed"
instead of "committed"?
In CVS and SVN those two were the same. With GIT it's really a push (to
trunk) we are interested in, not a commit to a
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108565
Andrew Pinski changed:
What|Removed |Added
Keywords||EH
--- Comment #2 from Andrew Pinski
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104338
--- Comment #12 from palmer at gcc dot gnu.org ---
I've got a somewhat recently rebased version of Patrick's patch floating
around, it passed testing but I got hung up on the futex_time64 thing and
forgot about it. Not sure if folks think it's
Pushed.
Gerald
---
htdocs/git.html | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/htdocs/git.html b/htdocs/git.html
index fc30c5ab..f71b451f 100644
--- a/htdocs/git.html
+++ b/htdocs/git.html
@@ -606,7 +606,7 @@ in Git (except for ones under
refs/vendors/).
tr29124
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108565
--- Comment #1 from Andrew Pinski ---
The missed optimization is because we don't optimize:
MEM[(int *)_28] = 2;
_8 = operator new (4);
[local count: 1073741825]:
MEM[(int *)_8] = 20;
MEM[(int *)_8] ={v} {CLOBBER};
operator
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108565
Bug ID: 108565
Summary: -Wuse-after-free false positive on a shared_ptr
implementation triggered by -O2
Product: gcc
Version: unknown
Status: UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105325
acsawdey at gcc dot gnu.org changed:
What|Removed |Added
CC||acsawdey at gcc dot
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104338
Andrew Pinski changed:
What|Removed |Added
CC||raj.khem at gmail dot com
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108564
Andrew Pinski changed:
What|Removed |Added
Resolution|--- |DUPLICATE
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108564
--- Comment #2 from Andrew Pinski ---
RISCV does not support subword atomics yet except via libatomic.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108564
Andrew Pinski changed:
What|Removed |Added
Component|c++ |target
Known to fail|13.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108564
Bug ID: 108564
Summary: RISCV std::atomic needs libatomics
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Snapshot gcc-10-20230126 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/10-20230126/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 10 git branch
with the following options: git://gcc.gnu.org/git/gcc.git branch
Here we crash because a CAST_EXPR, representing T(), doesn't have
its operand, and operand_equal_p's STRIP_ANY_LOCATION_WRAPPER doesn't
expect that. (o_e_p is called from warn_duplicated_cond_add_or_warn.)
In the past we've adjusted o_e_p to better cope with template codes,
but in this case I
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107952
--- Comment #19 from qinzhao at gcc dot gnu.org ---
(In reply to rguent...@suse.de from comment #11)
> > Agreed, usually where these extension should be documented?
>
> They are usually documented in doc/extend.texi
there is one section on
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108551
--- Comment #8 from Gaius Mulley ---
All git committed and pushed.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108563
Bug ID: 108563
Summary: [concepts] ICE (segfault) when requiring
sizeof(variable_tempalate_v)
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108562
Bug ID: 108562
Summary: [meta-bug] tracker bug for issues with
-Wanalyzer-null-dereference
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108555
Iain Sandoe changed:
What|Removed |Added
URL||https://gcc.gnu.org/piperma
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108519
--- Comment #3 from Alexander Monakov ---
Ah, a worthy sequel to "Note that I wasn't able to figure out a usable email
address for the submitter" from PR 107353. Nevermind then.
This has been retested on x86_64, powerpc64 linux-gnu (with 32b multilibs)
on i686, powerpc darwin (with 64b multilibs), x86_64 darwin with and
without 32b multilibs,
OK for trunk?
thanks
Iain
--- 8< ---
This is a partial reversion of the changes in r13-5373-g80cf2c5e8f496b.
As
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108463
--- Comment #6 from Jakub Jelinek ---
The first two differences are between insns 1204 vs. 1116 and 1204 vs. 1095:
(insn 1095 1094 1097 2 (set (mem/c:V4SI (plus:DI (reg/f:DI 7 sp)
(const_int -104 [0xff98])) [1 S16
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108463
--- Comment #5 from Jakub Jelinek ---
I've now tried:
--- sched-deps.cc.jj7 2023-01-19 09:58:50.971227752 +0100
+++ sched-deps.cc 2023-01-26 20:58:30.036035079 +0100
@@ -2498,7 +2498,10 @@ sched_analyze_1 (class deps_desc *deps,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108552
--- Comment #12 from Linus Torvalds ---
So it might be worth pointing explicitly to Vlastimil's email at
https://lore.kernel.org/all/2b857e20-5e3a-13ec-a0b0-1f69d2d04...@suse.cz/
which has annotated objdump output and seems to point to the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108519
--- Comment #2 from seurer at gcc dot gnu.org ---
I tried to test that patch but it didn't apply cleanly.
[u]int32_t are using different type between glibc and newlib, so getting
those node by int or long type isn't portable way, I also update all
other fixed-width integer types to prevent this happened again in future :P
gcc/ChangeLog:
* config/riscv/riscv-vector-builtins.cc
committed, thanks.
On Tue, Jan 10, 2023 at 7:41 AM wrote:
> From: Ju-Zhe Zhong
>
> gcc/testsuite/ChangeLog:
>
> * gcc.target/riscv/rvv/vsetvl/avl_single-1.c: New test.
> * gcc.target/riscv/rvv/vsetvl/avl_single-10.c: New test.
> *
committed, thanks.
On Tue, Jan 10, 2023 at 7:39 AM wrote:
> From: Ju-Zhe Zhong
>
> gcc/testsuite/ChangeLog:
>
> * gcc.target/riscv/rvv/vsetvl/avl_single-2.c: New test.
> * gcc.target/riscv/rvv/vsetvl/avl_single-20.c: New test.
> *
committed, thanks.
On Tue, Jan 10, 2023 at 7:36 AM wrote:
> From: Ju-Zhe Zhong
>
> gcc/testsuite/ChangeLog:
>
> * gcc.target/riscv/rvv/vsetvl/imm_bb_prop-3.c: Adjust testcase.
> * gcc.target/riscv/rvv/vsetvl/imm_bb_prop-4.c: Ditto.
> *
committed, thanks.
On Tue, Jan 10, 2023 at 7:11 AM wrote:
> From: Ju-Zhe Zhong
>
> gcc/ChangeLog:
>
> * config/riscv/riscv-vsetvl.cc (vector_insn_info::operator==):
> Remove dirty_pat.
> (vector_insn_info::merge): Ditto.
> (vector_insn_info::dump): Ditto.
>
committed, thanks.
On Tue, Jan 10, 2023 at 7:29 AM wrote:
> From: Ju-Zhe Zhong
>
> gcc/ChangeLog:
>
> * config/riscv/riscv-vsetvl.cc (same_bb_and_before_p): Remove it.
> (real_insn_and_same_bb_p): New function.
> (same_bb_and_after_or_equal_p): Remove it.
>
committed, thanks.
On Tue, Jan 10, 2023 at 7:17 AM wrote:
> From: Ju-Zhe Zhong
>
> Notice that the PASS is just simpily pick the probability >= 50%
> to do the backward fusion which will create endless loop on Phase 3.
>
> Adding this probability to fix this bug.
> gcc/ChangeLog:
>
> *
committed, thanks.
On Tue, Jan 10, 2023 at 6:57 AM wrote:
> From: Ju-Zhe Zhong
>
> Since the PASS is implemented base on RTL_SSA framework.
> According to rtl_ssa, they name insn_info * as insn and
> name rtx_insn * rinsn. I follow this rule in this pass but I missed
> this function. So rename
merged into another commit,, thanks.
On Tue, Jan 10, 2023 at 6:51 AM wrote:
> From: Ju-Zhe Zhong
>
> gcc/ChangeLog:
>
> * config/riscv/riscv-vsetvl.cc
> (pass_vsetvl::backward_demand_fusion): Add pre-check to avoid redundant
> flow.
>
> ---
> gcc/config/riscv/riscv-vsetvl.cc | 2 ++
>
committed, thanks.
On Tue, Jan 10, 2023 at 6:47 AM wrote:
> From: Ju-Zhe Zhong
>
> This NFC patch is preparing for the following patches.
> gcc/ChangeLog:
>
> * config/riscv/riscv-vsetvl.cc
> (pass_vsetvl::backward_demand_fusion): Refine codes.
>
> ---
>
committed, thanks.
On Tue, Jan 10, 2023 at 6:33 AM wrote:
> From: Ju-Zhe Zhong
>
> This patch is a NFC patch to move the codes into a wrapper function so that
> they can be reused. I will reuse them in the following patches.
>
> gcc/ChangeLog:
>
> * config/riscv/riscv-vsetvl.cc
>
committed, thanks.
On Tue, Jan 3, 2023 at 3:25 PM wrote:
> From: Ju-Zhe Zhong
>
> This patch is NFC patch. I move these code as a function since we will
> reuse it in the following patch (Refine phase 3 of VSETVL PASS)
>
> gcc/ChangeLog:
>
> * config/riscv/riscv-vsetvl.cc
committed with few tweaks, thanks.
On Wed, Jan 4, 2023 at 9:46 PM wrote:
> From: Ju-Zhe Zhong
>
> gcc/ChangeLog:
>
> * config/riscv/riscv-vsetvl.cc (can_backward_propagate_p): Fix for
> null iter_bb.
> (vector_insn_info::set_demand_info): New function.
>
committed, thanks.
On Tue, Jan 10, 2023 at 6:40 AM wrote:
> From: Ju-Zhe Zhong
>
> gcc/ChangeLog:
>
> * config/riscv/riscv-vsetvl.cc
> (pass_vsetvl::forward_demand_fusion): Add pre-check for redundant flow.
>
> ---
> gcc/config/riscv/riscv-vsetvl.cc | 8
> 1 file changed, 8
committed, thanks.
On Tue, Jan 3, 2023 at 3:17 PM wrote:
> From: Ju-Zhe Zhong
>
> gcc/ChangeLog:
>
> * config/riscv/riscv-vsetvl.cc (loop_basic_block_p): Adjust
> function.
> (backward_propagate_worthwhile_p): Fix non-worthwhile.
>
> ---
> gcc/config/riscv/riscv-vsetvl.cc | 91
committed, thanks.
On Tue, Jan 3, 2023 at 3:12 PM wrote:
> From: Ju-Zhe Zhong
>
> Since we only change insn which is not in group. The flag currently is not
> correct.
>
> gcc/ChangeLog:
>
> * config/riscv/riscv-vsetvl.cc (change_insn): Adjust in_group in
> validate_change.
>
> ---
>
committed, thanks.
On Tue, Jan 3, 2023 at 3:31 PM wrote:
> From: Ju-Zhe Zhong
>
> Suppose there are 2 demand infos:
>
> Demand 1: demand TAIL.
> Demand 2: not demand TAIL.
>
> If a block is demand 1, we should adjust this block is available both for
> demand 1 && 2.
> However, if a block is
committed, thanks.
On Thu, Dec 29, 2022 at 11:34 PM wrote:
> From: Ju-Zhe Zhong
>
> Currently we use pred_mov to to do the codegen for vse intrinsics.
> However, it
> generates inferior codegen when I am testing AVL model of VSETVL PASS
> using vse intrinsics.
>
> Consider this following code:
committed, thanks.
On Tue, Jan 3, 2023 at 2:56 PM wrote:
> From: Ju-Zhe Zhong
>
> Currently we support this optimization:
>
> bb 0:
> vsetvli a5,zero,e32,mf2
> bb 1:
> vsetvli a5,zero,e64,m1 --> vsetvli zero,zero,e64,m1
>
> According RVV ISA, we can do this optimization only if both RATIO
committed, thanks.
On Tue, Jan 3, 2023 at 9:40 AM wrote:
> From: Ju-Zhe Zhong
>
> Notice that we should used vsetivli zero,4 instead of vsetvli zero,4
> for IMM AVL (0 ~ 31) according to RVV ISA.
>
> This patch fix vsetivli instruction asm bug.
>
> gcc/ChangeLog:
>
> *
committed, thanks.
On Wed, Dec 28, 2022 at 1:11 PM wrote:
> From: Ju-Zhe Zhong
>
> For store intrinsic,
> the function type should be void store (T *...) instead of void store
> (const T *...)
>
> gcc/ChangeLog:
>
> * config/riscv/riscv-vector-builtins.cc: Change to scalar pointer.
>
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108544
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Target
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108552
Andrew Pinski changed:
What|Removed |Added
Ever confirmed|1 |0
Status|WAITING
OK, thanks for this :)
On Fri, Jan 27, 2023 at 12:40 AM Andreas Schwab via Gcc-patches <
gcc-patches@gcc.gnu.org> wrote:
> This follows the example of aarch64.
>
> gcc/:
> * common/config/riscv/riscv-common.cc
> (riscv_option_optimization_table)
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108543
Marek Polacek changed:
What|Removed |Added
Resolution|--- |FIXED
Summary|[10/11/12/13
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108551
Gaius Mulley changed:
What|Removed |Added
Attachment #54354|0 |1
is obsolete|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108543
--- Comment #6 from CVS Commits ---
The releases/gcc-12 branch has been updated by Marek Polacek
:
https://gcc.gnu.org/g:786923f74d6adfaf572f3d7c0307c51c522567f9
commit r12-9071-g786923f74d6adfaf572f3d7c0307c51c522567f9
Author: Marek Polacek
The recent gcc.dg/tree-ssa/clz-char.c test case failed for PRU target,
exposing a wrong code generation bug in the PRU backend. The "clz"
pattern did not produce correct output for QI and HI input operand
modes. SI mode is ok.
The "clz" pattern is expanded to an LMBD instruction to get the
The recent gcc.dg/tree-ssa/clz-char.c test case failed for PRU target,
exposing a wrong code generation bug in the PRU backend. The "clz"
pattern did not produce correct output for QI and HI input operand
modes. SI mode is ok.
The "clz" pattern is expanded to an LMBD instruction to get the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108544
--- Comment #4 from CVS Commits ---
The master branch has been updated by Harald Anlauf :
https://gcc.gnu.org/g:c8e07c7951421e718bcafbe5924e75c9aa133af9
commit r13-5400-gc8e07c7951421e718bcafbe5924e75c9aa133af9
Author: Harald Anlauf
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108463
--- Comment #4 from Jakub Jelinek ---
So, seems during the code added by above patch without the 0 && new_cselib_val
creates a value on DEBUG_INSNs for:
1) (mem:SI (plus:DI (reg/f:DI 7 sp)
(const_int NN)) [1 S4 A64])
for NN 76 to
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103506
--- Comment #6 from Steve Kargl ---
On Thu, Jan 26, 2023 at 02:56:02AM +, jvdelisle at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103506
>
> --- Comment #5 from Jerry DeLisle ---
> I found that the attached
On Thu, 26 Jan 2023, Jakub Jelinek wrote:
> On Thu, Jan 26, 2023 at 09:45:35AM -0500, Patrick Palka via Gcc-patches wrote:
> > > +#define DEFTREECODE(SYM, NAME, TYPE, LENGTH) TYPE,
> > > +#define END_OF_BASE_TREE_CODES tcc_exceptional,
> > > +
> > > +
> > > /* Class of tree given its code. */
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108543
--- Comment #5 from CVS Commits ---
The trunk branch has been updated by Marek Polacek :
https://gcc.gnu.org/g:a82ce9c8d155ecda2d1c647d5c588f29e21ef4a3
commit r13-5399-ga82ce9c8d155ecda2d1c647d5c588f29e21ef4a3
Author: Marek Polacek
Date:
hello,
could someone look at patch attached please?
https://gcc.gnu.org/pipermail/gcc-patches/2023-January/610147.html
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108561
--- Comment #4 from Jonathan Wakely ---
That changed with https://cplusplus.github.io/LWG/issue581 which I implemented
for GCC 12 in r12-1817-gf8c5b542f6cb6a so I guess you're looking at gcc-11 or
older.
hello,
could someone look at the patch attached please?
https://gcc.gnu.org/pipermail/gcc-patches/2023-January/610392.html
1 - 100 of 238 matches
Mail list logo
