https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87853
--- Comment #4 from Terry Guo ---
Thanks Derek for reporting. I can reproduce what Derek described and do think
this is a bug.
_mm_cmpgt_epi8 (__m128i __A, __m128i __B)
{
return (__m128i) ((__v16qi)__A > (__v16qi)__B);
}
This one performs
--
Sender:Richard Biener
Sent at:2018 Oct 31 (Wed) 17:11
To:bin.cheng ; Jan Hubicka
Cc:GCC Patches
Subject:Re: [PATCH AutoFDO/2]Treat ZERO as common profile probability/count
>
>
> On Wed, Oct 31, 2018 at 7:30 AM bin.cheng
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80744
Eric Gallager changed:
What|Removed |Added
Blocks||87403
Summary|Detect Divide
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80437
--- Comment #7 from Eric Gallager ---
(In reply to Markus Trippelsdorf from comment #6)
> (In reply to David Malcolm from comment #4)
> > If the warning is based of a const, maybe lead with that e.g. in the 2nd
> > place here:
> >
> >
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70831
Eric Gallager changed:
What|Removed |Added
CC||egallager at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=40503
Eric Gallager changed:
What|Removed |Added
CC||joseph at codesourcery dot com
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87079
sandra at gcc dot gnu.org changed:
What|Removed |Added
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed|
On 11/01/2018 08:25 PM, Paul Koning wrote:
I'm running the testsuite on the pdp11 target, and I get a failure when using
LRA that works correctly with the old allocator. The issue is that LRA is
producing an insn that is invalid (it violates the constraints stated in the
insn definition).
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70380
Eric Gallager changed:
What|Removed |Added
CC||jason at gcc dot gnu.org,
On 11/1/18 8:40 PM, Segher Boessenkool wrote:
> Hi Peter,
>
> On Thu, Nov 01, 2018 at 07:49:36PM -0500, Peter Bergner wrote:
>> On 11/1/18 7:25 PM, Paul Koning wrote:
>>> I'm running the testsuite on the pdp11 target, and I get a failure when
>>> using LRA that works correctly with the old
Ping ?
On Wed, Oct 31, 2018 at 8:30 PM Paul Hua wrote:
>
> Hi, GCC steering committee:
>
> There are some MIPS patches that need to be reviewed and approved.
>
> [PATCH v3 0/6] [MIPS] Reorganize the loongson march and extensions
> instructions set. [1]
> [PATCH v3 1/6] [MIPS] Split Loongson
Hi Peter,
On Thu, Nov 01, 2018 at 07:49:36PM -0500, Peter Bergner wrote:
> On 11/1/18 7:25 PM, Paul Koning wrote:
> > I'm running the testsuite on the pdp11 target, and I get a failure when
> > using LRA that works correctly with the old allocator. The issue is that
> > LRA is producing an
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87853
--- Comment #3 from Terry Guo ---
(In reply to H.J. Lu from comment #2)
> Xuepeng, can you take a look?
OK. Working on it now.
On 11/1/18 7:25 PM, Paul Koning wrote:
> I'm running the testsuite on the pdp11 target, and I get a failure when using
> LRA that works correctly with the old allocator. The issue is that LRA is
> producing an insn that is invalid (it violates the constraints stated in the
> insn definition).
I'm running the testsuite on the pdp11 target, and I get a failure when using
LRA that works correctly with the old allocator. The issue is that LRA is
producing an insn that is invalid (it violates the constraints stated in the
insn definition).
The insn in the IRA dump looks like this:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85035
sandra at gcc dot gnu.org changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
> So the current patch removes both the autoconf test and the uses of the
> macro. Solaris 11/SPARC Bootstraps with both as and gas currently
> running. Ok for mainline if they pass?
Sure, thanks for fixing this!
--
Eric Botcazou
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87858
--- Comment #1 from Matthew Krupcale ---
Created attachment 44945
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=44945=edit
analogous patch for GCC 8.2 potentially allowing future GCC to build GCC 8.2
(untested)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87858
Bug ID: 87858
Summary: Building old multilib bootstrap GCC: stage1 32-bit
libstdc++ fails to build after building 64-bit
libstdc++
Product: gcc
Version: unknown
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87852
Andrew Pinski changed:
What|Removed |Added
Keywords||wrong-code
Target Milestone|---
Snapshot gcc-7-20181101 is now available on
ftp://gcc.gnu.org/pub/gcc/snapshots/7-20181101/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 7 SVN branch
with the following options: svn://gcc.gnu.org/svn/gcc/branches/gcc-7
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87857
--- Comment #3 from Stas Sergeev ---
So a clang bug?
I wonder if ubsan is supposed to produce the
compile-time errors, rather than the run-time
warnings. Would it be possible to downgrade
this to a compile-time warning, and/or add a
switch to
On Thu, Nov 01, 2018 at 04:26:34PM -0400, Jason Merrill wrote:
> > @@ -16319,6 +16359,25 @@ cp_parser_template_name (cp_parser* parser,
> > if (TREE_CODE (*iter) == TEMPLATE_DECL)
> > found = true;
> >
> > + if (!found
> > + && (cxx_dialect > cxx17)
> > + &&
On 11/1/18 1:50 PM, Renlin Li wrote:
> Is there any update on this issues?
> arm-none-linux-gnueabihf native toolchain has been mis-compiled for a while.
>From the analysis I've done, my commit is just exposing latent issues
in LRA. Can you try the patch I submitted here to see if it helps?
Hi Chung-Lin!
On Mon, 10 Sep 2018 23:04:18 +0800, Chung-Lin Tang
wrote:
> This patch adds *_async versions of several OpenACC runtime library API
> functions,
> which is to allow execution of a function asynchronously on particular async
> stream, an addition to the standard since 2.5.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87857
--- Comment #2 from Andreas Schwab ---
1<<31 is undefined in C, but not in C++ (since C++14).
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87857
--- Comment #1 from Andrew Pinski ---
1 << 31 is undefined for C99 ...
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87857
Bug ID: 87857
Summary: case label does not reduce to an integer constant
Product: gcc
Version: 7.3.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
* config/aarch64/aarch64.opt (-matomic-ool): New.
* config/aarch64/aarch64.c (aarch64_atomic_ool_func): New.
(aarch64_ool_cas_names, aarch64_ool_swp_names): New.
(aarch64_ool_ldadd_names, aarch64_ool_ldset_names): New.
(aarch64_ool_ldclr_names,
This is the libgcc part of the interface -- providing the functions.
Rationale is provided at the top of libgcc/config/aarch64/lse.S.
* config/aarch64/lse-init.c: New file.
* config/aarch64/lse.S: New file.
* config/aarch64/t-lse: New file.
* config.host: Add t-lse
Do Not Merge Upstream.
This is for agraf and his testing within SLES.
---
gcc/common/config/aarch64/aarch64-common.c | 6 --
gcc/config/aarch64/aarch64.c | 6 --
2 files changed, 8 insertions(+), 4 deletions(-)
diff --git a/gcc/common/config/aarch64/aarch64-common.c
From: Richard Henderson
With aarch64_track_speculation, we had extra code to do exactly what the
!strong_zero_p path already did. The rest is reducing code duplication.
* config/aarch64/aarch64 (aarch64_split_compare_and_swap): Disable
strong_zero_p for
From: Richard Henderson
This pattern will only be used with the __sync functions, because
we do not yet have a bare TImode atomic load.
* config/aarch64/aarch64.c (aarch64_gen_compare_reg): Add support
for NE comparison of TImode values.
(aarch64_emit_load_exclusive):
From: Richard Henderson
* config/aarch64/aarch64.c (aarch64_print_operand): Allow integer
registers with %R.
---
gcc/config/aarch64/aarch64.c | 15 ---
1 file changed, 8 insertions(+), 7 deletions(-)
diff --git a/gcc/config/aarch64/aarch64.c
From: Richard Henderson
Changes since v2:
* Committed half of the patch set.
* Split inline TImode support from out-of-line patches.
* Removed the ST out-of-line functions, to match inline.
* Moved the out-of-line functions to assembly.
What I have not done, but is now a possibility, is
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=14557
--- Comment #22 from postmas...@flash-gordon-me-uk.bounceio.net ---
Your email was bounced...
-
... because something went wrong between you and your recipient. Oh
no!
What to do next?
On Fri, Nov 02, 2018 at 06:20:56AM +0900, Stafford Horne wrote:
> As we were getting ready for OpenRISC gcc port upstreaming Segher pointed out
> that we should be updating this.
>
> I don't think have CVS write access (only git binutils-gdb), can someone help
> to
> review and commit if OK?
I
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=14557
--- Comment #21 from felix ---
> va_list ap2;
> va_copy(ap2, ap);
> and then use , this always works.
> the proposed macros are both broken and unnecessary.
That's not equivalent. Using va_arg(ap2, T) does not propagate state changes
back to
Hello,
As we were getting ready for OpenRISC gcc port upstreaming Segher pointed out
that we should be updating this.
I don't think have CVS write access (only git binutils-gdb), can someone help to
review and commit if OK?
-Stafford
Index: readings.html
> On Nov 1, 2018, at 4:52 PM, Joseph Myers wrote:
>
> On Thu, 1 Nov 2018, Paul Koning wrote:
>
>> +@item inf
>> +Target supports floating point infinite (@code{inf}).
>> @end table
>
> Do you mean supports infinity for type double? (That's what the
> implementation does.) Supporting it
On Thu, 1 Nov 2018, Paul Koning wrote:
> +@item inf
> +Target supports floating point infinite (@code{inf}).
> @end table
Do you mean supports infinity for type double? (That's what the
implementation does.) Supporting it for double is not the same as
supporting it for float (SPU supports
Hi Renlin,
On Thu, Nov 01, 2018 at 06:50:22PM +, Renlin Li wrote:
> I got the following dump from the test case.
>
> x1 is an early clobber operand in the inline assembly statement,
> r92 should conflict with x1?
Yes, I think so. Or LRA should not pick something that was already a
hard
On Thu, Nov 1, 2018 at 3:36 PM Marek Polacek wrote:
> On Thu, Nov 01, 2018 at 12:15:48PM -0400, Jason Merrill wrote:
> > On 10/31/18 6:45 PM, Marek Polacek wrote:
> > > On Mon, Oct 29, 2018 at 05:59:13PM -0400, Jason Merrill wrote:
> > > > On 10/28/18 3:56 PM, Marek Polacek wrote:
> > > > > This
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54613
--- Comment #20 from Thomas Koenig ---
Author: tkoenig
Date: Thu Nov 1 20:12:57 2018
New Revision: 265732
URL: https://gcc.gnu.org/viewcvs?rev=265732=gcc=rev
Log:
2017-11-01 Thomas Koenig
PR fortran/54613
*
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87782
Thomas Koenig changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63426
Bug 63426 depends on bug 87782, which changed state.
Bug 87782 Summary: [9 Regression] runtime error: load of value 1818451807,
which is not a valid value for type 'expr_t'
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87782
What
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87782
--- Comment #4 from Thomas Koenig ---
Author: tkoenig
Date: Thu Nov 1 19:50:14 2018
New Revision: 265730
URL: https://gcc.gnu.org/viewcvs?rev=265730=gcc=rev
Log:
2018-11-01 Thomas Koenig
PR fortran/87782
* frontend-passes.c
On Wed, Oct 31, 2018 at 7:05 PM Joseph Myers
wrote:
> I've committed this revised patch version
Thank you for taking on this work.
> As noted, my expectation is that libgfortran, libgo, libgomp,
> liboffloadmic, libsanitizer, libphobos maintainers will deal with
> moving those directories to
On Thu, Nov 01, 2018 at 03:36:04PM -0400, Marek Polacek wrote:
> this hunk triggered an assert in tsubst_copy (just one testcase), but when
> I moved it, everything seemed to work well.
*removed*
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=40196
--- Comment #11 from Paul Thomas ---
Author: pault
Date: Thu Nov 1 19:36:08 2018
New Revision: 265729
URL: https://gcc.gnu.org/viewcvs?rev=265729=gcc=rev
Log:
2018-11-01 Paul Thomas
PR fortran/40196
* dependency.c
On Thu, Nov 01, 2018 at 12:15:48PM -0400, Jason Merrill wrote:
> On 10/31/18 6:45 PM, Marek Polacek wrote:
> > On Mon, Oct 29, 2018 at 05:59:13PM -0400, Jason Merrill wrote:
> > > On 10/28/18 3:56 PM, Marek Polacek wrote:
> > > > This patch implements P0846R0: ADL and Function Templates that are
A number of test cases fail on pdp11 because they use the "inf" float value
which does not exist on that target (nor on VAX). Rainer Orth and Joseph Myers
suggested adding a new effective-target keyword to check for this, and require
it for tests that have that dependency.
The attached patch
On Thu, Nov 1, 2018 at 9:13 PM Thomas Koenig wrote:
> Hello world,
>
> the attached patch fixes the PR by not trying to determine the length
> of the base symbol when there is a substring with a length which
> is not constant. This might make the length of temporary strings
> generated by the
Hello world,
the attached patch fixes the PR by not trying to determine the length
of the base symbol when there is a substring with a length which
is not constant. This might make the length of temporary strings
generated by the front end optimization pass shorter, while inserting
an
A number of test cases contain declarations like:
void *memcpy();
which currently are silently accepted on most platforms but not on all; pdp11
(and possibly some others) generate a "conflicting types for built-in function"
warning.
It was suggested to prune those messages because the test
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87856
Bug ID: 87856
Summary: Use subdir-objects in libgfortran automake
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component:
This patch fixes a number of test case failures on pdp11. Some are too large
for the address space, some have dependencies on the float format that don't
match the DEC format, some add pdp11 to the targets that expect particular
compiler messages.
Committed.
paul
ChangeLog:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87782
Thomas Koenig changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |tkoenig at gcc dot
gnu.org
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87782
Thomas Koenig changed:
What|Removed |Added
Status|NEW |ASSIGNED
CC|
Hi Peter,
Is there any update on this issues?
arm-none-linux-gnueabihf native toolchain has been mis-compiled for a while.
I got the following dump from the test case.
x1 is an early clobber operand in the inline assembly statement,
r92 should conflict with x1?
;; a0(r93,l0) conflicts:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=46020
--- Comment #13 from Thomas Koenig ---
Author: tkoenig
Date: Thu Nov 1 18:41:28 2018
New Revision: 265727
URL: https://gcc.gnu.org/viewcvs?rev=265727=gcc=rev
Log:
2018-11-01 Thomas Koenig
PR fortran/46020
*
This fixes some test suite failures due to a missing arithmetic support routine.
Committed.
paul
ChangeLog:
2018-11-01 Paul Koning
* config/pdp11/t-pdp11 (LIB2ADD): Add divmod.c.
(HOST_LIBGCC2_CFLAGS): Change to optimize for size.
Index: config/pdp11/t-pdp11
On 11/1/18 2:06 PM, Marek Polacek wrote:
Ping.
On Thu, Oct 11, 2018 at 09:28:38PM -0400, Marek Polacek wrote:
Recently it came up that no test in the testsuite triggers the RANGE_FOR_STMT
case in potential_constant_expression_1. I came up with this valid test that
tickles that codepath.
I
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87855
Ville Voutilainen changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
Ping.
On Thu, Oct 11, 2018 at 09:28:38PM -0400, Marek Polacek wrote:
> Recently it came up that no test in the testsuite triggers the RANGE_FOR_STMT
> case in potential_constant_expression_1. I came up with this valid test that
> tickles that codepath.
>
> I can't use ({ }) instead of a lambda
On Tue, Oct 30, 2018 at 9:36 PM H.J. Lu wrote:
> > Why not at the expand time? Rewrite vector constant as vec_duplicate
> > from memory and combine will do the stuff for you. We do have _bcst
> > instruction patterns.
> >
>
> Here is the updated patch to do that. OK for trunk?
Looks mostly
On Tue, Oct 30, 2018 at 10:12 AM Wei Xiao wrote:
>
> Hi,
>
> The attached patch updates VFIXUPIMM* Intrinsics to align with the
> latest Intel® 64 and IA-32 Architectures Software Developer’s Manual
> (SDM).
> Tested with GCC regression test on x86, no regression.
A couple of remarks:
On Thu, 1 Nov 2018, Rainer Orth wrote:
> * One for ia64 in gcc_cv_as_ia64_ltoffx_ldxmov_relocs) ...
>
> $as_echo '.text
> addl r15 = @ltoffx(x#), gp
> ;;
> ld8.mov r16 = [r15], x#'[] > conftest.s
Thanks for pointing this out. I've applied this patch to fix this by
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87853
H.J. Lu changed:
What|Removed |Added
CC||xuepeng.guo at intel dot com
--- Comment #2
The test fails for msp430-elf which has 16-bit int by default. The test
uses __INT32_TYPE__ in place of int, when __SIZEOF_INT__ < 4.
gcc.dg/tree-ssa/cunroll-13.c: In function 't':
gcc.dg/tree-ssa/cunroll-13.c:13:1: error: type mismatch in binary expression
13 | t (struct a * a)
| ^
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87853
Uroš Bizjak changed:
What|Removed |Added
CC||hjl.tools at gmail dot com
--- Comment #1
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87855
Bug ID: 87855
Summary: std::optional only copy-constructible if T is
trivially copy-constructible
Product: gcc
Version: 8.1.0
Status: UNCONFIRMED
Severity:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82857
--- Comment #3 from Tom de Vries ---
The dwz man shows:
...
-M NAME --multifile-name NAME
Specify the name of the common file that should be put into the
.gnu_debugaltlink section alongside
with its build
The autoconf 2.69 upgrade broke Solaris/SPARC bootstrap with as:
compiling stage1 libgcc fails with an assembler error:
/usr/ccs/bin/as: "/var/tmp//ccYQ2Dxc.s", line 32: error: detect global register
use not covered .register pseudo-op
/usr/ccs/bin/as: "/var/tmp//ccYQ2Dxc.s", line 32: error:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82857
Ian Lance Taylor changed:
What|Removed |Added
CC||ian at airs dot com
--- Comment #2
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82857
Tom de Vries changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
Hello!
v2 of the patch hits the real problem: in pass_expand::execute
finish_eh_generation is called after expand_stack_alignment is called.
Construction of SjLj landing pads calls emit_library_call, which can
change crtl->preferred_stack_boundary value after all dependant
variables are already
On 10/31/18 6:45 PM, Marek Polacek wrote:
On Mon, Oct 29, 2018 at 05:59:13PM -0400, Jason Merrill wrote:
On 10/28/18 3:56 PM, Marek Polacek wrote:
This patch implements P0846R0: ADL and Function Templates that are not Visible
Hi,
I understand that you are one of the Exhibitors of "Consumer Electronics
Show - CES 2019" taking place on DEC 8 - 11, 2019, at Las Vegas, NV.
I was wondering if you would be interested in acquiring Consumer Electronics
Show - CES 2019 - Attendees List for booth invites, drive
Hi!
On Thu, Nov 01, 2018 at 09:00:08AM -0500, Aaron Sawdey wrote:
> (rs6000_address_for_fpconvert) Combine with
> rs6000_force_indexed_or_indirect_mem.
(missing colon)
> rtx
> -rs6000_address_for_fpconvert (rtx x)
> +rs6000_force_indexed_or_indirect_mem (rtx x)
> {
> - rtx addr;
Ping?
Best regards,
Thomas
On Fri, 26 Oct 2018 at 22:41, Thomas Preudhomme
wrote:
>
> Hi,
>
> Please find updated patch to fix PR85434: spilling of stack protector
> guard's address on ARM. Quite a few changes have been made to the ARM
> part since last round of review so I think it makes more
2017-10-31 Mike Gulick
PR preprocessor/83173
* gcc/input.c (dump_location_info): Dump reason and
included_from fields from line_map_ordinary struct. Fix
indentation when location > 5 digits.
* libcpp/location-example.txt: Update example
2018-10-31 Mike Gulick
PR preprocessor/83173
* gcc.dg/plugin/location-overflow-test-pr83173.c: New test.
* gcc.dg/plugin/location-overflow-test-pr83173.h: Header for
pr83173.c.
* gcc.dg/plugin/location-overflow-test-pr83173-1.h: Header for
Hi,
Changes in v3:
I haven't gotten a response in several months, so I'm reposting these
patches. I split up the enhancement to the -fdump-internal-locations
output from the actual bugfix. Hopefully this will make these easier to
review. I rebased these patches on the gcc master and had to
2018-10-31 Mike Gulick
PR preprocessor/83173
* libcpp/files.c (_cpp_stack_include): Check if
line_table->highest_location is past current line before
decrementing.
---
libcpp/files.c | 32 +++-
1 file changed, 23 insertions(+), 9
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58372
--- Comment #40 from Uroš Bizjak ---
(In reply to Terry Guo from comment #39)
> (In reply to Uroš Bizjak from comment #38)
> > (In reply to Terry Guo from comment #36)
> >
> > > OK. Do it right now.
> >
> > I think that latest attachment is
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87854
Bug ID: 87854
Summary: [9 Regression] gcc.c-torture/compile/pr46534.c ICE for
16-bit size_t
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87843
--- Comment #5 from Jan Hubicka ---
I think this is caused by misoptimizing
void **x;
void *info ATTRIBUTE_UNUSED;
{
cselib_val *v = (cselib_val *)*x;
struct elt_loc_list **p = >locs;
int had_locs = v->locs != 0;
while (*p)
Ping...
For this patch here: https://gcc.gnu.org/ml/gcc-patches/2018-10/msg01336.html
Thanks
Bernd.
On 10/22/18 5:08 PM, Bernd Edlinger wrote:
> Hi!
>
> This makes c_strlen avoid an unsafe strlen folding of const arguments
> with non-const offset. Currently a negative out of bounds offset
>
Ping...
I'd like to ping this patch:
https://gcc.gnu.org/ml/gcc-patches/2018-10/msg01335.html
Thanks
Bernd.
On 10/22/18 4:59 PM, Bernd Edlinger wrote:
> Hi!
>
> This fixes an ICE which was exposed by a previous patch of mine,
> and a wrong transformation from strcat_chk => strcpy_chk,
> which
Ping...
On 10/10/18 9:43 PM, Bernd Edlinger wrote:
> Ping...
>
>
> On 08/26/18 21:40, Bernd Edlinger wrote:
>> Ping...
>>
>> This is just plain wrong, independent
>> of any STRING_CST semantic issues.
>>
>> The original patch (retested on current trunk) is
>> here:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87853
Bug ID: 87853
Summary: _mm_cmpgt_epi8 broken with -funsigned-char
Product: gcc
Version: 7.3.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87852
Martin Liška changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87844
Marek Polacek changed:
What|Removed |Added
Target Milestone|--- |7.4
Summary|ICE in
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87844
Marek Polacek changed:
What|Removed |Added
Keywords||ice-on-invalid-code
On Wed, Oct 31, 2018 at 4:56 AM Richard Biener wrote:
>
> On Tue, 30 Oct 2018, Richard Biener wrote:
>
> >
> > This picks up work from earlier this year where Aldy worked on
> > undoing forwprop during out-of-SSA to improve coalescing across
> > backedges.
> >
> > The following patch first
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87852
Bug ID: 87852
Summary: [9 Regression] FAIL: gcc.c-torture/execute/pr53465.c
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87840
--- Comment #9 from Martin Liška ---
(In reply to Jan Engelhardt from comment #8)
> g++-9 from openSUSE devel:gcc, the rest from Tumbleweed, SVN numbers see -v
> banners above.
Ok, the trunk version is before libsanitizer merge. Please try it
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87840
--- Comment #8 from Jan Engelhardt ---
g++-9 from openSUSE devel:gcc, the rest from Tumbleweed, SVN numbers see -v
banners above.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87851
Thomas Koenig changed:
What|Removed |Added
CC||jb at gcc dot gnu.org
1 - 100 of 187 matches
Mail list logo
