On Wed, Jul 26, 2023 at 01:54:01PM +0800, Kewen.Lin wrote:
> Hi Mike,
>
> on 2023/7/11 03:59, Michael Meissner wrote:
> > In doing other work, I noticed that there was an insn:
> >
> > vsx_extract_v4sf__load
> >
> > Which did not have an iterator. I removed the useless .
>
> It actually ha
Hi Mike,
on 2023/7/11 03:59, Michael Meissner wrote:
> In doing other work, I noticed that there was an insn:
>
> vsx_extract_v4sf__load
>
> Which did not have an iterator. I removed the useless .
It actually has a mode iterator, the "P" is used for clobber.
The whole pattern of this de
On Mon, Jul 10, 2023 at 03:10:21PM -0500, Segher Boessenkool wrote:
> Hi!
>
> On Mon, Jul 10, 2023 at 03:59:44PM -0400, Michael Meissner wrote:
> > In doing other work, I noticed that there was an insn:
> >
> > vsx_extract_v4sf__load
> >
> > Which did not have an iterator. I removed the use
Hi!
On Mon, Jul 10, 2023 at 03:59:44PM -0400, Michael Meissner wrote:
> In doing other work, I noticed that there was an insn:
>
> vsx_extract_v4sf__load
>
> Which did not have an iterator. I removed the useless .
This patch does that, you mean.
> --- a/gcc/config/rs6000/vsx.md
> +++ b/
On Wed, Nov 16, 2022 at 8:29 AM Kewen.Lin wrote:
>
> Hi,
>
> As Robin spotted, my recent commit r13-3716 caused an ICE
> on s390 if vector access with length is enabled there (his
> patch for the enablement hasn't been committed yet). The
> failure is caused by one stupid typo, the bias on s390 i
On 9/23/22 12:43, Torbjörn SVENSSON via Gcc-patches wrote:
The "RISC-V specific attributes" section should be at the same level
as "PowerPC-specific attributes".
gcc/ChangeLog:
* doc/sourcebuild.texi: Fix chapter level.
OK
jeff
On December 22, 2021 1:03:18 PM GMT+01:00, "Martin Liška"
wrote:
>Hello.
>
>The patch is quite obvious fix.
>
>Patch can bootstrap on x86_64-linux-gnu and survives regression tests.
>
>Ready to be installed?
Ok.
Richard.
>Thanks,
>Martin
>
> PR ipa/103786
>
>gcc/ChangeLog:
>
> *
On Thu, Nov 25, 2021 at 9:00 AM liuhongt via Gcc-patches
wrote:
>
> TYPE_PRECISION (type) < TYPE_PRECISION (TREE_TYPE (@2)) supposed to check
> integer type but not pointer type, so use second parameter instead.
>
> i.e. first parameter is VPTR, second parameter is I4.
>
> 582DEF_SYNC_BUILTIN (BU
On Sun, Aug 08, 2021 at 03:21:02PM -0500, Segher Boessenkool wrote:
> On Thu, Aug 05, 2021 at 10:44:36PM -0400, Michael Meissner wrote:
> > * gcc.target/powerpc/fold-vec-load-builtin_vec_xl-char.c: Fix
> > typo in regular expression.
> > * gcc.target/powerpc/fold-vec-load-builtin_vec_xl
On Thu, Aug 05, 2021 at 10:44:36PM -0400, Michael Meissner wrote:
> * gcc.target/powerpc/fold-vec-load-builtin_vec_xl-char.c: Fix
> typo in regular expression.
> * gcc.target/powerpc/fold-vec-load-builtin_vec_xl-double.c:
> Likewise.
> * gcc.target/powerpc/fold-vec-loa
Hi Mike,
FWIW, looks fine to me, if tests are all passing now.
Bill
On 8/5/21 9:44 PM, Michael Meissner wrote:
[PATCH] Fix typo in fold-vec-load-builtin_vec_xl-* tests.
When I checked in the fix for running tests on power10 systems with
power10 code generation, I had a typo in the
fold-vec-lo
Hi:
pushed to master.
Remove xfail for pr92658-avx512vl.c
Typo of standard pattern name has been fixed by r12-1970, remove those
xfails.
gcc/testsuite/ChangeLog
* gcc.target/i386/pr92658-avx512vl.c: Refine testcase.
diff --git a/gcc/testsuite/gcc.target/i386/pr92
This caused
XPASS: gcc.target/i386/pr92658-avx512vl.c scan-assembler-times vpmovqw 2
FAIL: gcc.target/i386/pr92658-avx512vl.c scan-assembler-times vpmovdw 1
XPASS: gcc.target/i386/pr92658-avx512vl.c scan-assembler-times vpmovdw 2
liuhongt via Gcc-patches 于2021年7月1日周四 下午3:45写道：
>
> Bootstrapped
On 3/7/2021 4:10 PM, Ahamed Husni via Gcc-patches wrote:
Hi all,
This is my first contribution for an open source project. Please guide
me if anything is missing.
diff --git a/gcc/gcc/asan.c b/gcc/gcc/asan.c
index 89ecd99b182..836f50bd44a 100755
--- a/gcc/gcc/asan.c
+++ b/gcc/gcc/asan.c
@
On Thu, 21 Jan 2021 at 14:39, Kyrylo Tkachov wrote:
>
>
>
> > -Original Message-
> > From: Gcc-patches On Behalf Of
> > Christophe Lyon via Gcc-patches
> > Sent: 21 January 2021 13:37
> > To: gcc-patches@gcc.gnu.org
> > Subject: [PATCH] Fix typo in arm_mve.h __arm_vcmpneq_s8 return type
>
> -Original Message-
> From: Gcc-patches On Behalf Of
> Christophe Lyon via Gcc-patches
> Sent: 21 January 2021 13:37
> To: gcc-patches@gcc.gnu.org
> Subject: [PATCH] Fix typo in arm_mve.h __arm_vcmpneq_s8 return type
>
> Like all vcmp intrinsics, __arm_vcmpneq_s8 should return a mve_p
Qian Jianhua writes:
> This patch fixes a typo in the document of GCC Internals.
Pushed to trunk, thanks.
Richard
>
> ---
> gcc/doc/generic.texi | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/gcc/doc/generic.texi b/gcc/doc/generic.texi
> index 827c4232aef..fb98727928a
On Thu, Jun 4, 2020 at 8:09 AM Hongtao Liu via Gcc-patches
wrote:
>
> This patch to is fix uppercase of mode in trunc2, it
> should be lowercase for standard pattern name.
>
> Bootstrap is ok, regression test on i386/x86-64 backend is ok.
OK.
Richard.
> gcc/ChangeLog:
> * config/i386/
on 2020/1/13 下午6:46, Richard Sandiford wrote:
> "Kewen.Lin" writes:
>> Hi,
>>
>> Function average_num_loop_insns forgets to free loop body in early return.
>> Besides, overflow comparison checks 100 (e6) but the return value is
>> 10 (e5), I guess it's unexpected, a typo?
>>
>> Bootstrap
"Kewen.Lin" writes:
> Hi,
>
> Function average_num_loop_insns forgets to free loop body in early return.
> Besides, overflow comparison checks 100 (e6) but the return value is
> 10 (e5), I guess it's unexpected, a typo?
>
> Bootstrapped and regress tested on powerpc64le-linux-gnu.
> I
On Wed, Nov 27, 2019 at 11:32:24AM +0800, Hongtao Liu wrote:
> hi jakub:
> VF is used for differentiating AVX512F/AVX/SSE, but there's
> condition TARGET_AVX512F in avx512f_maskcmp3, it must be a TYPO
> and should be VF_AVX512VL instead.
>
> Bootstrap and regression test on i386/x86_64 backend i
Hi any feedback on this?
Thanks.
On Tue, Jul 23, 2019 at 02:49:13PM -0400, Arvind Sankar wrote:
> There seems to be a typo in gcc/jit/Make-lang.in where it references an
> undefined LIBGCCJIT_SYMLINK instead of LIBGCCJIT_SONAME_SYMLINK.
> ---
> gcc/jit/Make-lang.in | 5 ++---
> 1 file changed, 2
On Fri, May 31, 2019 at 3:43 PM Martin Liška wrote:
>
> Hi.
>
> I've been working on an overhaul of IPA ICF and I noticed that issue.
>
> Looks to me obvious.
>
> Patch can bootstrap on x86_64-linux-gnu and survives regression tests.
>
> Ready to be installed?
OK.
Richard.
> Thanks,
> Martin
>
On 10/4/18 2:58 AM, Richard Biener wrote:
> On Wed, 3 Oct 2018, Christophe Lyon wrote:
>
>> On Mon, 1 Oct 2018 at 11:36, Richard Biener wrote:
>>>
>>>
>>> The following typo-fix happens to fix a --param max-peel-branches limit
>>> caused missed peeling. The typo is present everywhere, the missed
On Wed, 3 Oct 2018, Christophe Lyon wrote:
> On Mon, 1 Oct 2018 at 11:36, Richard Biener wrote:
> >
> >
> > The following typo-fix happens to fix a --param max-peel-branches limit
> > caused missed peeling. The typo is present everywhere, the missed
> > peeling is a regression from GCC 7.
> >
>
On Mon, 1 Oct 2018 at 11:36, Richard Biener wrote:
>
>
> The following typo-fix happens to fix a --param max-peel-branches limit
> caused missed peeling. The typo is present everywhere, the missed
> peeling is a regression from GCC 7.
>
> Bootstrap and regtest running on x86_64-unknown-linux-gnu.
Giuliano Augusto Faulin Belinassi writes:
> There was a small typo in the current version of trunk, more precisely
> in genmatch.c and exp_unst.ads. This patch fixes it.
>
> Changelog:
>
> 2018-08-23 Giuliano Belinassi
>
> * genmatch.c: Fix typo 'exapnded' to 'expanded'.
> * exp_unst.ads
On Mon, Jun 11, 2018 at 09:05:26AM +0200, Martin Liška wrote:
> Hi.
>
> This is typo I did when MPX was removed. I'm moving back hunk with
> BUILT_IN_STPCPY_CHK.
>
> Ready after testing?
> Martin
>
> gcc/ChangeLog:
>
> 2018-06-11 Martin Liska
>
> PR tree-optimization/86089
>
On 24/11/17 18:03 +0100, Stephan Bergmann wrote:
Otherwise, at least recent Clang trunk with -std=gnu++17 complains
In file included from
lib/gcc/x86_64-pc-linux-gnu/8.0.0/../../../../include/c++/8.0.0/functional:60:
In file included from
lib/gcc/x86_64-pc-linux-gnu/8.0.0/../../../../include/
On Mon, Jul 31, 2017 at 04:37:19PM +0300, Ville Voutilainen wrote:
> On 31 July 2017 at 16:25, Marek Polacek wrote:
> > The documentation of std::stack says that the underlying container must
> > support
> > pop_front, but that is wrong, it meant to say pop_back, so this patch fixes
> > that.
>
On 31 July 2017 at 16:25, Marek Polacek wrote:
> The documentation of std::stack says that the underlying container must
> support
> pop_front, but that is wrong, it meant to say pop_back, so this patch fixes
> that.
Indeed, the documentation has a copy-pasto originating from bits/stl_queue.h.
On 02/21/2017 10:52 AM, Jakub Jelinek wrote:
> On Tue, Feb 21, 2017 at 10:44:40AM +0100, Martin Liška wrote:
>> The patch is obvious, however should I also replace the option in *.po files:
>
> Ok for trunk.
>
>> gcc/po/be.po:msgid "Known assembler dialects (for use with the
>> -masm-dialect= op
On Tue, Feb 21, 2017 at 10:44:40AM +0100, Martin Liška wrote:
> The patch is obvious, however should I also replace the option in *.po files:
Ok for trunk.
> gcc/po/be.po:msgid "Known assembler dialects (for use with the -masm-dialect=
> option):"
> gcc/po/da.po:msgid "Known assembler dialects (
Here it is.
gcc/
* config/i386/i386.c (m_SKYLAKE_AVX512): Fix typo.
Yulia
On Tue, Nov 3, 2015 at 5:32 PM, Uros Bizjak wrote:
> On Tue, Nov 3, 2015 at 3:16 PM, Yulia Koval wrote:
>> Hi,
>>
>> This patch fixes a typo: PROCESSOT -> PROCESSOR. Ok for trunk?
>
> Trivial patch, OK with a suitabl
On Tue, Nov 3, 2015 at 3:16 PM, Yulia Koval wrote:
> Hi,
>
> This patch fixes a typo: PROCESSOT -> PROCESSOR. Ok for trunk?
Trivial patch, OK with a suitable ChangeLog.
Uros.
On 07/13/2015 11:00 AM, Marek Polacek wrote:
While working on a new warning I found this typo.
Bootstrapped/regtested on x86_64-linux, ok for trunk?
2015-07-13 Marek Polacek
* rtl.c (rtx_equal_p_cb): Fix typo.
OK.
jeff
On Sun, 10 May 2015 22:07:53 -0600, Jeff Law wrote:
> On 05/10/2015 03:00 PM, Paulo Matos wrote:
> Yes. This would fall under the obvious rule and can be committed
> without waiting for approvals.
>
> jeff
Thanks. Committed.
--
Paulo Matos
On 05/10/2015 03:00 PM, Paulo Matos wrote:
OK to commit?
2015-05-10 Paulo Matos
* configure.ac: Fix typo.
* configure: Regenerate.
Yes. This would fall under the obvious rule and can be committed
without waiting for approvals.
jeff
Hi Benno,
I tested your fixes on i386-unknown-freebsd10.1 -- you never
know, after some of these could have been reflected in some
test case for example -- and committed them on your behalf.
Sorry for none of us looking into this for so long. If you
find further typos or phrases that need improv
On Fri, Mar 27, 2015 at 10:55:48AM +0100, Marek Polacek wrote:
> Ok?
Sure, it is obvious.
> 2015-03-27 Marek Polacek
>
> * gimple-iterator.h (gsi_prev_nondebug): Fix typo.
>
> diff --git gcc/gimple-iterator.h gcc/gimple-iterator.h
> index 6be88dd..9aa7508 100644
> --- gcc/gimple-iterat
On March 11, 2015 2:32:18 PM CET, Marek Polacek wrote:
>This patch fixes a pretty obvious typo: we couldn't possibly want to
>test
>whether a variable equals itself. PR c/54979 is an RFE for a warning
>that
>would detect such cases.
>
>Bootstrapped/regtested on x86_64-linux, ok for active branche
On 10/13/14 20:49, Kito Cheng wrote:
Hi Marc:
- -1 if it is not a cost classe. */
+ -1 if it is not a cost classes. */
"a cost class", no plural here.
Thank you for correcting me :)
Hi Jeff:
Thanks, and updated patch in attachment,
However I don't have commit right yet, can you
Hi Marc:
>> - -1 if it is not a cost classe. */
>> + -1 if it is not a cost classes. */
>
> "a cost class", no plural here.
Thank you for correcting me :)
Hi Jeff:
Thanks, and updated patch in attachment,
However I don't have commit right yet, can you help me to commit it? thanks.
Fr
On Mon, 13 Oct 2014, Kito Cheng wrote:
- -1 if it is not a cost classe. */
+ -1 if it is not a cost classes. */
"a cost class", no plural here.
--
Marc Glisse
On 10/13/14 02:09, Kito Cheng wrote:
Hi all:
This patch contain lots typo fix for IRA module by aspell :)
ChangeLog
2014-10-13 Kito Cheng
* ira.c: Fix typo in comment.
* ira.h: Ditto.
* ira-build.c: Ditto.
* ira-color.c: Ditto.
* ira-emit.c: Dit
On 09/25/14 08:04, Felix Yang wrote:
Please apply this patch if OK for trunk. Thanks.
[ ... ]
Index: gcc/ChangeLog
===
--- gcc/ChangeLog(revision 215598)
+++ gcc/ChangeLog(working copy)
@@ -1,3 +1,8 @@
+2014-09-25 Felix Ya
On 2014-02-06 21:18, Benno Schulenberg wrote:
> Updating a bit the Dutch translations of GCC's messages,
> I noticed the following mistakes in three msgids:
>
> "only displayed one" ==> "displayed only once"
> "none class-method" ==> "non-class method"
> "incorect" ==> "incorrect"
Pin
On Fri, Jan 03, 2014 at 01:03:24PM +0100, Marek Polacek wrote:
> __builtin_{FILE,FUNCTION} had wrong return types, thus fixed.
> Tested by make html and links -g. Ok for trunk?
Ok, thanks.
> 2014-01-03 Marek Polacek
>
> PR other/59661
> * doc/extend.texi: Fix the return value of
On 11/26/13 05:59, Alexander Ivchenko wrote:
Hi,
The patch addresses the issue Jan-Benedict's buildrobot found:
http://gcc.gnu.org/ml/gcc/2013-11/msg00507.html
diff --git a/gcc/ChangeLog b/gcc/ChangeLog
index 7704433..da9a3e2 100644
--- a/gcc/ChangeLog
+++ b/gcc/ChangeLog
@@ -1,3 +1,7 @@
+201
> -Original Message-
> From: Marek Polacek [mailto:pola...@redhat.com]
> Sent: 24 September 2013 14:52
> To: Paulo Matos
> Cc: gcc-patches@gcc.gnu.org
> Subject: Re: [PATCH] Fix typo in check for null
>
> On Tue, Sep 24, 2013 at 01:44:30PM +, Paulo Matos w
On Tue, Sep 24, 2013 at 01:44:30PM +, Paulo Matos wrote:
> Thanks for the comments Marek, will fix it.
>
> 2013-09-24 Paulo Matos
^^
Two spaces between name and . Sorry for nitpicking like
this. Thanks!
Marek
> -Original Message-
> From: Richard Biener [mailto:richard.guent...@gmail.com]
> Sent: 24 September 2013 10:03
> To: Paulo Matos
> Cc: gcc-patches@gcc.gnu.org
> Subject: Re: [PATCH] Fix typo in check for null
>
> On Mon, Sep 23, 2013 at 4:03 PM, Paulo Matos wr
> -Original Message-
> From: Marek Polacek [mailto:pola...@redhat.com]
> Sent: 24 September 2013 13:57
> To: Paulo Matos
> Cc: gcc-patches@gcc.gnu.org
> Subject: Re: [PATCH] Fix typo in check for null
>
> On Mon, Sep 23, 2013 at 02:03:02PM +, Paulo Matos wrote:
On Mon, Sep 23, 2013 at 02:03:02PM +, Paulo Matos wrote:
> This is a patch for master, where in number_of_loops, we want to check if the
> loops (returned by loops_for_fn) is non-null but instead we are using fn,
> which is the function argument. I haven't opened a bug report, please let me
On Mon, Sep 23, 2013 at 4:03 PM, Paulo Matos wrote:
> This is a patch for master, where in number_of_loops, we want to check if the
> loops (returned by loops_for_fn) is non-null but instead we are using fn,
> which is the function argument. I haven't opened a bug report, please let me
> know i
On 06/20/2013 09:09 PM, Roland Lutz wrote:
> Signed-off-by: Roland Lutz
> ---
> libjava/contrib/aot-compile.in |2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/libjava/contrib/aot-compile.in b/libjava/contrib/aot-compile.in
> index 91cfc67..2ee6739 100644
> --- a/lib
On Fri, May 17, 2013 at 02:46:56PM +0200, Richard Biener wrote:
>
> stmt_kills_ref_p_1 wants to compare MEM_REF offset but compares
> the pointers instead (which are previously compared as equal).
> This breaks my fix for PR57303.
>
> Fixed thus, applied as obvious.
>
> Richard.
>
> 2013-05-17
On May 22, 2012, at 7:17 PM, Richard Henderson wrote:
> On 05/15/12 01:52, Tristan Gingold wrote:
>> 2012-05-14 Tristan Gingold
>>
>> * common/config/ia64/ia64-common.c (ia64_except_unwind_info): Fix typo.
>
> Ok.
Thanks, committed.
Tristan.
On 05/15/12 01:52, Tristan Gingold wrote:
> 2012-05-14 Tristan Gingold
>
> * common/config/ia64/ia64-common.c (ia64_except_unwind_info): Fix typo.
Ok.
r~
On Oct 18, 2011, at 4:23 PM, David Edelsohn wrote:
> Tristan,
>
> Mike fixed the typo already. Why are you still seeing a problem?
Indeed, was fixed later.
Tristan.
>
> - David
>
> On Tue, Oct 18, 2011 at 6:52 AM, Tristan Gingold wrote:
>> Ping…
>>
>> On Oct 13, 2011, at 5:11 PM, Tristan
Tristan,
Mike fixed the typo already. Why are you still seeing a problem?
- David
On Tue, Oct 18, 2011 at 6:52 AM, Tristan Gingold wrote:
> Ping…
>
> On Oct 13, 2011, at 5:11 PM, Tristan Gingold wrote:
>
>> Hi,
>>
>> looks like an obvious typo. Ok for trunk ?
>>
>> Tristan.
>>
>> 2011-10-13
Ping…
On Oct 13, 2011, at 5:11 PM, Tristan Gingold wrote:
> Hi,
>
> looks like an obvious typo. Ok for trunk ?
>
> Tristan.
>
> 2011-10-13 Tristan Gingold
>
> * config/rs6000/rs6000.c (rs6000_init_builtins): Fix typo.
>
> diff --git a/gcc/config/rs6000/rs6000.c b/gcc/config/rs6000/
On 07/14/2011 01:44 PM, Richard Guenther wrote:
> On Thu, Jul 14, 2011 at 1:41 PM, Matthias Klose wrote:
>> fix a typo in doc/extend.texi, committed as obvious.
>
> Specify the architecture to generate code for when compiling the
> -function. If you select the @code{"target("cpu=power7)"} attri
On Thu, Jul 14, 2011 at 1:41 PM, Matthias Klose wrote:
> fix a typo in doc/extend.texi, committed as obvious.
Specify the architecture to generate code for when compiling the
-function. If you select the @code{"target("cpu=power7)"} attribute when
+function. If you select the @code{"target("cp
64 matches
Mail list logo
