On 06/02/2018 20:16, François Dumont wrote:
On 05/02/2018 18:16, Jonathan Wakely wrote:
Wouldn't it make more sense to simply make __aligned_buffer identical
to __aligned_membuf for the versioned-namespace? Then at least the
conditional code is only in one place.
Yes, __aligned_buffer is
Hi!
Unfortunately, seems my rest_of_insert_endbranch fix doesn't fix
-fcompare-debug on the testcase, when adding the endbr after the setjmp
call with no note in between, we add it into the same bb as the setjmp call,
while when adding it with -g with NOTE_INSN_CALL_ARG_LOCATION, which is
already
On 02/06/2018 08:59 AM, Martin Sebor wrote:
> On 02/06/2018 06:23 AM, Marek Polacek wrote:
>> On Tue, Feb 06, 2018 at 01:57:36PM +0100, Jakub Jelinek wrote:
>>> On Tue, Feb 06, 2018 at 01:46:21PM +0100, Marek Polacek wrote:
--- gcc/testsuite/c-c++-common/Wstringop-truncation-3.c
+++
On 02/06/2018 05:57 AM, Jakub Jelinek wrote:
> On Tue, Feb 06, 2018 at 01:46:21PM +0100, Marek Polacek wrote:
>> --- gcc/testsuite/c-c++-common/Wstringop-truncation-3.c
>> +++ gcc/testsuite/c-c++-common/Wstringop-truncation-3.c
>> @@ -0,0 +1,20 @@
>> +/* PR tree-optimization/84228 */
>> +/* {
On 02/06/2018 05:46 AM, Marek Polacek wrote:
> When -Wstringop-truncation sees a strncpy call where the specified bound
> is equal to the size of the destination, it looks at the next statement
> to see if it's dst[i] = '\0';, and if it is, it doesn't warn. But it
> needs to look at the next
On 02/02/2018 02:35 PM, David Malcolm wrote:
> On Thu, 2018-02-01 at 12:05 +0100, Richard Biener wrote:
>> On Wed, Jan 31, 2018 at 4:39 PM, David Malcolm
>> wrote:
>>> PR 84136 reports an ICE within sccvn_dom_walker when handling a
>>> C/C++ source file that overuses the
On 02/01/2018 04:05 AM, Richard Biener wrote:
> On Wed, Jan 31, 2018 at 4:39 PM, David Malcolm wrote:
>> PR 84136 reports an ICE within sccvn_dom_walker when handling a
>> C/C++ source file that overuses the labels-as-values extension.
>> The code in question stores a jump
On 01/31/2018 08:39 AM, David Malcolm wrote:
> PR 84136 reports an ICE within sccvn_dom_walker when handling a
> C/C++ source file that overuses the labels-as-values extension.
> The code in question stores a jump label into a global, and then
> jumps to it from another function, which ICEs after
On 02/06/2018 02:38 AM, Aldy Hernandez wrote:
> The -Walloca pass can receive a malformed alloca, courtesy of someone
> providing a faulty prototype. This was causing an ICE because we
> assumed alloca calls had at least one argument, which the testcase does
> not:
>
> +void *alloca ();
>
On 02/07/2018 12:06 AM, Richard Biener wrote:
> On February 6, 2018 9:40:37 PM GMT+01:00, Jakub Jelinek
> wrote:
>> Hi!
>>
>> As the following testcase shows, dom2 miscompiles floating point x - x
>> into 0.0 even when x could be infinity and x - x then a NaN.
>> The
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84266
--- Comment #3 from Bill Seurer ---
All the compilation failures disappear if the two casts
/home/seurer/gcc/build/gcc-trunk/gcc/include/mmintrin.h:857:5: error:
incompatible types when assigning to type '__vector signed int' {aka
'__vector(4)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84276
--- Comment #2 from Steve Kargl ---
On Thu, Feb 08, 2018 at 02:26:50AM +, sgk at troutmask dot
apl.washington.edu wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84276
>
> --- Comment #1 from Steve Kargl ---
> Reduced testcase.
>
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82930
sandthorn changed:
What|Removed |Added
CC||hotguest1 at hotmail dot com
--- Comment #3
I went ahead and changed all the options on the list below
to include LTO and tested the attached patch by configuring
with --with-build-config=bootstrap-lto --disable-werror and
making profiledbootstrap. Attached, besides the patch, is
also the breakdown of warnings. The interesting column is
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84276
--- Comment #1 from Steve Kargl ---
Reduced testcase.
subroutine stepns(hh,h,s,w)
real, intent(inout) :: h,hh,s
real, intent(out) :: w
real :: qofs
qofs(s)=s
w=qofs(hh+h)
end subroutine stepns
Problem
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84258
David Malcolm changed:
What|Removed |Added
Status|ASSIGNED|WAITING
--- Comment #4 from David
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84276
kargl at gcc dot gnu.org changed:
What|Removed |Added
Priority|P3 |P4
Known to fail|
PR c/84258 reports that we issue this:
warning: format is a wide character string [-Wformat=]
on this code:
const unsigned char cuc[] = "%i";
sprintf(buf, (char *)cuc, 1);
despite the absence of wide characters.
This wording dates back 17.5 years to r36586:
2000-09-24 Joseph S. Myers
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84276
Bug ID: 84276
Summary: Invalid error for valid statement function
Product: gcc
Version: 8.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: fortran
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84275
Bug ID: 84275
Summary: missing warning on conflicting attributes on different
declara
Product: gcc
Version: 8.0
Status: UNCONFIRMED
Severity: normal
On Thu, 2018-02-08 at 01:17 +0100, Marc Glisse wrote:
> On Wed, 7 Feb 2018, Paul Smith wrote:
> > > > My question is, what do I need to do to ensure this behavior
> > > > persists if I create a global operator new/delete?
> > > >
> > > > Is it sufficient to ensure that the symbol for our shared
>
Hi Richard,
On 1 February 2018 at 23:21, Richard Biener wrote:
> On Thu, Feb 1, 2018 at 5:07 AM, Kugan Vivekanandarajah
> wrote:
>> Hi Richard,
>>
>> On 31 January 2018 at 21:39, Richard Biener
>>
On Wed, 2018-02-07 at 16:38 -0700, Martin Sebor wrote:
> I'm not sure I see how defining operator new inline can work
> unless you recompile the world (i.e., all the DSOs used by
> the program, including libstdc++). As Marc already hinted,
> if libstdc++ dynamically allocates an object using the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84274
Bug ID: 84274
Summary: [feature request] mbind attribute
Product: gcc
Version: 8.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
On Wed, 7 Feb 2018, Paul Smith wrote:
My question is, what do I need to do to ensure this behavior
persists if I create a global operator new/delete?
Is it sufficient to ensure that the symbol for our shared library
global new/delete symbols are hidden and not global, using a linker
map or
On Wed, Feb 07, 2018 at 05:26:49PM -0600, Segher Boessenkool wrote:
> On Wed, Feb 07, 2018 at 05:48:26PM -0500, Michael Meissner wrote:
> > This patch udpates the GCC installation documentation to document the
> > configuration options to set the long double type on the PowerPC: I verified
> >
On 7 February 2018 at 23:38, Martin Sebor wrote:
> On 02/06/2018 03:56 PM, Paul Smith wrote:
>>
>> Hi all.
>>
>> Hopefully this isn't too annoying a question :).
>>
>> My environment has been using GCC 6.2 (locally compiled) on GNU/Linux
>> systems. We use a separate heap management library
On Feb 5, 2018, at 8:42 AM, Douglas Mencken wrote:
>
> I’m about
>
> “ [PATCH 2/4] [Darwin,PPC] Remove uses of LR in
> restore_world ” https://gcc.gnu.org/bugzilla/attachment.cgi?id=42304
>
> look at bug #84113 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84113 for
>
On 02/06/2018 03:56 PM, Paul Smith wrote:
Hi all.
Hopefully this isn't too annoying a question :).
My environment has been using GCC 6.2 (locally compiled) on GNU/Linux
systems. We use a separate heap management library (jemalloc) rather
than the libc allocator. The way we did this in the
On Wed, Feb 07, 2018 at 05:23:31PM -0600, Will Schmidt wrote:
> > > /* { dg-do compile { target { powerpc64le-*-* && lp64 } } } */
> > > /* { dg-skip-if "" { powerpc*-*-darwin* } } */
> > > /* { dg-require-effective-target powerpc_vsx_ok } */
> > > -/* { dg-options "-mvsx -O2" } */
> > > +/* {
On Wed, Feb 07, 2018 at 05:48:26PM -0500, Michael Meissner wrote:
> This patch udpates the GCC installation documentation to document the
> configuration options to set the long double type on the PowerPC: I verified
> that the documentation builds. Can I install this on to the trunk?
Yes
On Wed, 2018-02-07 at 12:28 -0600, Segher Boessenkool wrote:
> Hi!
>
> On Wed, Feb 07, 2018 at 11:16:12AM -0600, Will Schmidt wrote:
> > Noted during review of test results on P9. Due to changes and
> > improvements,
> > our codegen is different for this test on power9.
> > Modified the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84154
Michael Meissner changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
> Indeed, this solves most of the new failures. Here is the acats test
> summary:
> === acats Summary ===
> # of expected passes 2298
> # of unexpected failures 22
> *** FAILURES: c23003b c23003g c23003i c250002 c380004 cd2b11a cd2b15c
> ce2102l ce2102m ce2103a ce2103b
On Wed, 2018-02-07 at 12:02 -0600, Segher Boessenkool wrote:
> Hi,
>
> On Wed, Feb 07, 2018 at 10:59:46AM -0600, Will Schmidt wrote:
> > Noted during review of test results on P9. The vsxcopy.c test is looking
> > for lxvd2x, stxvd2x instructions in generated code. For P9 targets, we will
> >
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84154
--- Comment #3 from Michael Meissner ---
Author: meissner
Date: Wed Feb 7 22:54:59 2018
New Revision: 257470
URL: https://gcc.gnu.org/viewcvs?rev=257470=gcc=rev
Log:
[gcc]
2018-02-07 Michael Meissner
PR
This patch udpates the GCC installation documentation to document the
configuration options to set the long double type on the PowerPC: I verified
that the documentation builds. Can I install this on to the trunk?
2018-02-07 Michael Meissner
*
On Wed, Feb 07, 2018 at 03:52:39PM -0500, Jason Merrill wrote:
> > E.g. the constexpr function uses same_type_ignoring_top_level_qualifiers_p
> > instead of == type comparisons, the COMPONENT_REF stuff, ...
>
> > For poly_* stuff, I think Richard S. wants to introduce it into the FEs at
> > some
Hi!
As mentioned in the PR, the vt_get_decl_and_offset function verifies
incoming PARALLEL is usable for tracking, but if it fails, we retry
vt_get_decl_and_offset on DECL_RTL and there we check only that a memory
isn't larger than 16 bytes (to make sure it doesn't have more than 16
parts), but
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82994
--- Comment #6 from kargl at gcc dot gnu.org ---
Author: kargl
Date: Wed Feb 7 22:41:59 2018
New Revision: 257468
URL: https://gcc.gnu.org/viewcvs?rev=257468=gcc=rev
Log:
2018-02-07 Steven G. Kargl
PR
Snapshot gcc-6-20180207 is now available on
ftp://gcc.gnu.org/pub/gcc/snapshots/6-20180207/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 6 SVN branch
with the following options: svn://gcc.gnu.org/svn/gcc/branches/gcc-6
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82994
kargl at gcc dot gnu.org changed:
What|Removed |Added
Status|NEW |RESOLVED
Hi Mike,
On Tue, Feb 06, 2018 at 04:34:08PM -0500, Michael Meissner wrote:
> Here is the patch reworked. It bootstraps on both little/big endian power8,
> and all of the tests run. Can I install this into trunk now, and into GCC 7
> after a soak period (along with the previous patch)?
> +;; If
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83707
--- Comment #3 from Will Schmidt ---
Created attachment 43360
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=43360=edit
.expand dump from a build with -O1.
the .expand dump from a build with -O1.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82994
--- Comment #5 from kargl at gcc dot gnu.org ---
Author: kargl
Date: Wed Feb 7 22:36:24 2018
New Revision: 257467
URL: https://gcc.gnu.org/viewcvs?rev=257467=gcc=rev
Log:
2018-02-07 Steven G. Kargl
PR
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83707
Will Schmidt changed:
What|Removed |Added
CC||willschm at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84082
--- Comment #6 from Jakub Jelinek ---
Author: jakub
Date: Wed Feb 7 22:30:51 2018
New Revision: 257466
URL: https://gcc.gnu.org/viewcvs?rev=257466=gcc=rev
Log:
PR c++/84082
* parser.c (cp_parser_dot_deref_incomplete): New
Committed as obvious.
2018-02-07 Steven G. Kargl
PR fortran/82994
* match.c (gfc_match_deallocate): Check for NULL pointer.
2018-02-07 Steven G. Kargl
PR fortran/82994
* gfortran.dg/deallocate_error_3.f90: New test.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82994
--- Comment #4 from kargl at gcc dot gnu.org ---
Author: kargl
Date: Wed Feb 7 22:29:22 2018
New Revision: 257465
URL: https://gcc.gnu.org/viewcvs?rev=257465=gcc=rev
Log:
2018-02-07 Steven G. Kargl
PR
Hello, gentle maintainer.
This is a message from the Translation Project robot.
A revised PO file for textual domain 'gcc' has been submitted
by the Spanish team of translators. The file is available at:
http://translationproject.org/latest/gcc/es.po
(This file, 'gcc-8.1-b20180128.es.po',
On Thu, Feb 1, 2018 at 9:12 AM, Max Filippov wrote:
> On Wed, Jan 31, 2018 at 11:17 AM, Max Filippov wrote:
>> On Wed, Jan 31, 2018 at 11:11 AM, augustine.sterl...@gmail.com
>> wrote:
>>> On Tue, Jan 30, 2018 at 8:02 PM, Max
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82478
Alexander Zaitsev changed:
What|Removed |Added
CC||zamazan4ik at tut dot by
---
This patch changes the libgo runtime package to not call funcPC from a
function. The escape analysis support is not yet good enough to avoid
escaping the argument to funcPC. This causes unnecessary and often
harmful memory allocation. E.g., (*cpuProfile).addExtra can be called
from a signal
On 02/07/2018 12:11 PM, Daniel Berlin wrote:
Note that the ABI is explicitly designed so that type identity can be done
by address comparison.
correct, but be aware that lots of dynamic objects seem to step outside
the ABI by building shared objects with -Bsymbolic[1], or the equivalent
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84273
Bug ID: 84273
Summary: Reject allocatable passed-object dummy argument
(proc_ptr_47.f90)
Product: gcc
Version: 8.0
Status: UNCONFIRMED
Severity: normal
On Wed, Feb 07, 2018 at 08:36:31PM +0100, Marek Polacek wrote:
> > > That was my first patch, but it was rejected:
> > > https://gcc.gnu.org/ml/gcc-patches/2018-01/msg00271.html
> >
> > Then should we update fold_indirect_ref_1 to use the new code? Is
> > there a reason for them to stay out of
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83390
--- Comment #8 from Vladimir Makarov ---
(In reply to David Binderman from comment #0)
> A build of today's gcc trunk with valgrind produces this:
>
> ==8995== Conditional jump or move depends on uninitialised value(s)
> ==8995==at
OK.
On Wed, Feb 7, 2018 at 4:16 PM, Paolo Carlini wrote:
> Hi,
>
> this is essentially an RFC, I'm still fully analyzing the issue, but since I
> already have something prima facie reasonable and passing the testsuite I
> decided to send immediately out what I have,
On Wed, Feb 7, 2018 at 4:14 PM, Jakub Jelinek wrote:
> On Wed, Feb 07, 2018 at 03:52:39PM -0500, Jason Merrill wrote:
>> > E.g. the constexpr function uses same_type_ignoring_top_level_qualifiers_p
>> > instead of == type comparisons, the COMPONENT_REF stuff, ...
>>
>> > For
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84218
Neil Carlson changed:
What|Removed |Added
CC||neil.n.carlson at gmail dot com
---
Hi,
this is essentially an RFC, I'm still fully analyzing the issue, but
since I already have something prima facie reasonable and passing the
testsuite I decided to send immediately out what I have, looking for
further feedback / help. As fully analyzed by Jakub in the audit trail,
for the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84270
Harald Anlauf changed:
What|Removed |Added
CC||anlauf at gmx dot de
--- Comment #1
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84272
Martin Liška changed:
What|Removed |Added
Priority|P3 |P1
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84272
Bug ID: 84272
Summary: AddressSanitizer: heap-use-after-free
../../gcc/config/aarch64/cortex-a57-fma-steering.c:519
in fma_node::get_parity()
Product: gcc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68560
--- Comment #28 from Thomas Koenig ---
Author: tkoenig
Date: Wed Feb 7 21:08:51 2018
New Revision: 257462
URL: https://gcc.gnu.org/viewcvs?rev=257462=gcc=rev
Log:
2018-02-07 Thomas Koenig
PR fortran/68560
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82049
kargl at gcc dot gnu.org changed:
What|Removed |Added
Status|NEW |RESOLVED
Thanks. A version of the patch has been commit to 6-branch,
7-branch, and trunk. One regression down, many more to go.
--
steve
On Wed, Feb 07, 2018 at 08:10:41AM +, Paul Richard Thomas wrote:
> Hi Steve,
>
> That's OK for trunk and, if you are possessed of the intestinal
> fortitude, 6-
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82049
--- Comment #5 from kargl at gcc dot gnu.org ---
Author: kargl
Date: Wed Feb 7 21:01:00 2018
New Revision: 257461
URL: https://gcc.gnu.org/viewcvs?rev=257461=gcc=rev
Log:
2018-02-07 Steven G. Kargl
PR
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78303
--- Comment #4 from Segher Boessenkool ---
If -maltivec=be is not used, I support removing it. Deprecating it with a
warning on use will show if anyone care enough to tell us they do use it ;-)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69558
David Malcolm changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned
On Wed, Feb 7, 2018 at 3:32 PM, Jakub Jelinek wrote:
> On Wed, Feb 07, 2018 at 03:23:25PM -0500, Jason Merrill wrote:
>> On Wed, Feb 7, 2018 at 2:48 PM, Jakub Jelinek wrote:
>> > On Wed, Feb 07, 2018 at 08:36:31PM +0100, Marek Polacek wrote:
>> >> > > That was
On Wed, Feb 07, 2018 at 09:42:04PM +0100, Thomas Koenig wrote:
> Here's an update on the patch - I realized that it is not necessary
> to check for the actual argument, it is always present.
>
> OK for trunk?
>
Yes.
--
Steve
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82049
--- Comment #4 from kargl at gcc dot gnu.org ---
Author: kargl
Date: Wed Feb 7 20:45:40 2018
New Revision: 257460
URL: https://gcc.gnu.org/viewcvs?rev=257460=gcc=rev
Log:
2018-02-07 Steven G. Kargl
PR
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82049
--- Comment #3 from kargl at gcc dot gnu.org ---
Author: kargl
Date: Wed Feb 7 20:43:33 2018
New Revision: 257459
URL: https://gcc.gnu.org/viewcvs?rev=257459=gcc=rev
Log:
2018-02-06 Steven G. Kargl
PR
On Wed, Feb 07, 2018 at 03:23:25PM -0500, Jason Merrill wrote:
> On Wed, Feb 7, 2018 at 2:48 PM, Jakub Jelinek wrote:
> > On Wed, Feb 07, 2018 at 08:36:31PM +0100, Marek Polacek wrote:
> >> > > That was my first patch, but it was rejected:
> >> > >
Here's an update on the patch - I realized that it is not necessary
to check for the actual argument, it is always present.
OK for trunk?
Regards
Thomas
2018-02-01 Thomas Koenig
PR fortran/68560
* trans-intrinsic.c (gfc_conv_intrinsic_shape): New
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83204
Paolo Carlini changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned
> "Dan" == Daniel Berlin writes:
Dan> If there are multiple types named Foo<2u>, DWARF needs to be extended to
Dan> allow a pointer from the vtable debug info to the class type debug info
Dan> (unless they already added one).
This is what we did for Rust.
Rust doesn't
On Wed, Feb 7, 2018 at 2:48 PM, Jakub Jelinek wrote:
> On Wed, Feb 07, 2018 at 08:36:31PM +0100, Marek Polacek wrote:
>> > > That was my first patch, but it was rejected:
>> > > https://gcc.gnu.org/ml/gcc-patches/2018-01/msg00271.html
>> >
>> > Then should we update
On 02/07/2018 08:37 PM, Rainer Orth wrote:
Hi Tom,
this patch fixes an 8 regression in an openacc testcase.
The regression was introduced by r250925, a fix for PR78266, a bug in the
handling of a loop with iteration variable type range smaller than the size
of the parallel dimension the loop
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84266
--- Comment #2 from Bill Schmidt ---
I wonder how many failures are left if that invalid cast is removed from the
code? It is just wrong and unnecessary.
On 02/06/2018 11:01 PM, Martin Sebor wrote:
On 02/05/2018 02:52 PM, Jason Merrill wrote:
On 02/04/2018 07:07 PM, Martin Sebor wrote:
To resolve the underlying root cause of the P1 bug c++/83503
- bogus -Wattributes for const and pure on function template
specialization, that we discussed last
Hi Tom,
> this patch fixes an 8 regression in an openacc testcase.
>
> The regression was introduced by r250925, a fix for PR78266, a bug in the
> handling of a loop with iteration variable type range smaller than the size
> of the parallel dimension the loop is assigned to.
>
> The fix for the
On Wed, Feb 07, 2018 at 01:23:49PM -0500, Jason Merrill wrote:
> On Wed, Feb 7, 2018 at 12:54 PM, Marek Polacek wrote:
> > On Wed, Feb 07, 2018 at 12:26:04PM -0500, Jason Merrill wrote:
> >> On Fri, Jan 26, 2018 at 6:22 PM, Jakub Jelinek wrote:
> >> > On
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84212
Martin Sebor changed:
What|Removed |Added
Keywords||patch
--- Comment #6 from Martin Sebor
In PR 84212 the reporter asks why -Wno-stringop-overflow has
no effect during LTO linking. It turns out that the reason
is the same as in bug 78768: the specification in the c.opt
file is missing LTO among the languages.
The attached patch adds LTO to it and to -Wstringop-truncation.
On 02/06/2018 11:02 PM, Alexandre Oliva wrote:
On Feb 6, 2018, Jason Merrill wrote:
On 12/11/2017 09:52 PM, Alexandre Oliva wrote:
Why do we need to use a non-zero view identifier for a zero view? Why
can't we always use 0 instead of the bitmap?
We assign view ids
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84220
Peter Bergner changed:
What|Removed |Added
Status|UNCONFIRMED |ASSIGNED
URL|
On Wed, 2018-02-07 at 17:26 +, Nick Clifton wrote:
> Hi Martin, Hi David,
>
> OK - attached is a new patch that:
>
> * Replaces control characters with their escape equivalents.
> * Includes a testcase.
>
> I was not sure what to do about the inconsistencies between the
> behaviour of
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84270
Bug ID: 84270
Summary: optimization bug with assumed size array argument
Product: gcc
Version: 7.3.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Hi All,
The previous testcase would fail on a system where the initial mode is thumb
and later
switches to an arm mode. This would again cause some warnings to be emitted.
This patch visits all builtins defined with builtin_define_with_int_value and
undefines
them if they could possibly change
Hi!
On Wed, Feb 07, 2018 at 11:16:12AM -0600, Will Schmidt wrote:
> Noted during review of test results on P9. Due to changes and improvements,
> our codegen is different for this test on power9.
> Modified the existing test to target P8, and added a P9 variant with updated
> counts.
> diff
On 2018-02-07 12:30, Jonathan Wakely wrote:
Ah ok, the class name appears mangled in other entities' mangled name.
But
from what I understand there's no mangled name for the class such that
echo | c++filt
outputs the class name (e.g. "Foo<10>"). That wouldn't make sense,
since
there's
On Wed, 2018-02-07 at 13:22 -0500, Jason Merrill wrote:
> On Wed, Feb 7, 2018 at 1:12 PM, David Malcolm
> wrote:
> > On Wed, 2018-02-07 at 12:21 -0500, Jason Merrill wrote:
> > > On Fri, Jan 26, 2018 at 1:12 PM, David Malcolm > > om>
> > > wrote:
> > > >
On Wed, Feb 7, 2018 at 12:54 PM, Marek Polacek wrote:
> On Wed, Feb 07, 2018 at 12:26:04PM -0500, Jason Merrill wrote:
>> On Fri, Jan 26, 2018 at 6:22 PM, Jakub Jelinek wrote:
>> > On Fri, Jan 26, 2018 at 02:11:19PM +0100, Richard Biener wrote:
>> >> >>
On Wed, Feb 7, 2018 at 1:12 PM, David Malcolm wrote:
> On Wed, 2018-02-07 at 12:21 -0500, Jason Merrill wrote:
>> On Fri, Jan 26, 2018 at 1:12 PM, David Malcolm
>> wrote:
>> > On Mon, 2017-12-11 at 17:24 -0500, Jason Merrill wrote:
>> > > On Wed, Nov 22,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81419
David Malcolm changed:
What|Removed |Added
Status|NEW |ASSIGNED
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83789
--- Comment #4 from Segher Boessenkool ---
Kaushik: is this fixed with r256762?
On Wed, 2018-02-07 at 12:21 -0500, Jason Merrill wrote:
> On Fri, Jan 26, 2018 at 1:12 PM, David Malcolm
> wrote:
> > On Mon, 2017-12-11 at 17:24 -0500, Jason Merrill wrote:
> > > On Wed, Nov 22, 2017 at 10:36 AM, David Malcolm > > com>
> > > wrote:
> >
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80567
David Malcolm changed:
What|Removed |Added
See Also||https://gcc.gnu.org/bugzill
1 - 100 of 299 matches
Mail list logo