https://gcc.gnu.org/bugzilla/show_bug.cgi?id=44803
Eric Gallager changed:
What|Removed |Added
Status|UNCONFIRMED |WAITING
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=33915
Eric Gallager changed:
What|Removed |Added
Status|UNCONFIRMED |WAITING
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85764
--- Comment #1 from Jason Merrill ---
Author: jason
Date: Sat Jun 2 03:14:44 2018
New Revision: 261101
URL: https://gcc.gnu.org/viewcvs?rev=261101=gcc=rev
Log:
PR c++/85764 - bogus 'this' not captured error.
* lambda.c
Here, because we're inside a member function, resolvable_dummy_lambda
thought we could resolve a reference to 'this'. But because it's a
static member function, we can't. Using nonlambda_method_basetype
instead of current_nonlambda_class_type fixes that, but then I needed
to improve n_m_b to
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86026
Rich Felker changed:
What|Removed |Added
CC||bugdal at aerifal dot cx
--- Comment #4
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85975
kargl at gcc dot gnu.org changed:
What|Removed |Added
Target Milestone|--- |8.2
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85816
kargl at gcc dot gnu.org changed:
What|Removed |Added
Status|NEW |RESOLVED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85975
kargl at gcc dot gnu.org changed:
What|Removed |Added
Status|NEW |RESOLVED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85816
Bug 85816 depends on bug 85975, which changed state.
Bug 85975 Summary: Incorrect size for spread array
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85975
What|Removed |Added
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85816
--- Comment #3 from kargl at gcc dot gnu.org ---
Author: kargl
Date: Sat Jun 2 01:07:46 2018
New Revision: 261099
URL: https://gcc.gnu.org/viewcvs?rev=261099=gcc=rev
Log:
2018-06-01 Steven G. Kargl
PR fortran/85816
PR
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85975
--- Comment #5 from kargl at gcc dot gnu.org ---
Author: kargl
Date: Sat Jun 2 01:07:46 2018
New Revision: 261099
URL: https://gcc.gnu.org/viewcvs?rev=261099=gcc=rev
Log:
2018-06-01 Steven G. Kargl
PR fortran/85816
PR
The new mangling scheme for PowerPC now uses "u9__ieee128" as the mangled name
instead of "U10__float128". This would break old code that used __float128 and
called to libraries built with the new compiler.
This patch adds a hook to emit a weak reference for the old mangled name when
we are
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85764
Paolo Carlini changed:
What|Removed |Added
Priority|P3 |P2
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85995
--- Comment #5 from joseph at codesourcery dot com ---
On Fri, 1 Jun 2018, vincent-gcc at vinc17 dot net wrote:
> Programmers normally use conditionals on '__STDC__' to ask whether
> it is safe to use certain features of ISO C, such
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67711
Jason Merrill changed:
What|Removed |Added
Keywords|wrong-code |diagnostic
Status|NEW
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85873
Bug 85873 depends on bug 67445, which changed state.
Bug 67445 Summary: New warning: returning std::initializer_list bound to
temporary
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67445
What|Removed |Added
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67445
Jason Merrill changed:
What|Removed |Added
Status|NEW |RESOLVED
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85873
Jason Merrill changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85995
--- Comment #4 from Vincent Lefèvre ---
(In reply to jos...@codesourcery.com from comment #3)
> See trouble.texi, "Non-bugs" / "Certain Changes We Don't Want to Make",
> "Undefining @code{__STDC__} when @option{-ansi} is not used."
which
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85873
--- Comment #4 from Jason Merrill ---
Author: jason
Date: Fri Jun 1 22:48:58 2018
New Revision: 261091
URL: https://gcc.gnu.org/viewcvs?rev=261091=gcc=rev
Log:
PR c++/85873 - constant initializer_list array not in .rodata.
*
Snapshot gcc-8-20180601 is now available on
ftp://gcc.gnu.org/pub/gcc/snapshots/8-20180601/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 8 SVN branch
with the following options: svn://gcc.gnu.org/svn/gcc/branches/gcc-8
On Fri, 1 Jun 2018, Michael Meissner wrote:
> I'm wondering if there are other suggestions to make this patch acceptable.
>
> As I mentioned previously, the initialization process needs to go through all
> of the widening tables in order to initialize all FP types, so we can't just
> arbitrarily
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86011
--- Comment #2 from Patrick Oppenlander ---
Sure,
# cat test.c
struct foo { long a, b; };
struct foo test(long long x)
{
return (struct foo){x / 77, x % 77};
}
# gcc --version
gcc (GCC) 8.1.0
Copyright (C) 2018 Free Software Foundation,
On Fri, 2018-06-01 at 17:31 +0200, Richard Biener wrote:
> On June 1, 2018 3:40:15 PM GMT+02:00, David Malcolm com> wrote:
> > On Fri, 2018-06-01 at 11:50 +0200, Richard Biener wrote:
> > > On Tue, May 29, 2018 at 10:33 PM David Malcolm > > om>
> > > wrote:
> > > >
> > > > This was an
On Fri, Jun 01, 2018 at 09:33:57PM +, Joseph Myers wrote:
> On Fri, 1 Jun 2018, Segher Boessenkool wrote:
>
> > This patch changes the (C++) mangling of the 128-bit float types.
> > IBM long double ("double-double") is mangled as "g", as before, and
> > IEEE 128-bit long double is mangled as
On Fri, 1 Jun 2018, Segher Boessenkool wrote:
> This patch changes the (C++) mangling of the 128-bit float types.
> IBM long double ("double-double") is mangled as "g", as before, and
> IEEE 128-bit long double is mangled as "u9__ieee128".
To be clear: given this mangling (which certainly
OK.
On Fri, Jun 1, 2018 at 8:29 AM, Mark Wielaard wrote:
> On Sat, 2018-05-26 at 21:31 +0200, Mark Wielaard wrote:
>> The loclists_base attribute is used to point to the beginning of the
>> loclists index of a DWARF5 loclists table when using DW_FORM_loclistsx.
>> For split compile units the
On Fri, Jun 1, 2018 at 5:03 PM, Paolo Carlini wrote:
> while working on some bugs I noticed that in a few places in decl.c we could
> do better in terms of locations within the current infrastructure, some
> simple, straightforward improvements. I'm attaching below a tiny first
> patch, more to
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86029
ktkachov at gcc dot gnu.org changed:
What|Removed |Added
CC||ktkachov at gcc dot gnu.org
On Thu, May 31, 2018 at 02:57:57PM -0500, Will Schmidt wrote:
> 2018-05-31 Will Schmidt
>
> * gcc.target/powerpc/fold-vec-store-vec_xst-char.c : New.
> * gcc.target/powerpc/fold-vec-store-vec_xst-double.c : New.
> * gcc.target/powerpc/fold-vec-store-vec_xst-float.c : New.
On Thu, May 31, 2018 at 02:58:40PM -0500, Will Schmidt wrote:
> 2018-05-31 Will Schmidt
>
> * gcc.target/powerpc/p8-vec-xl-xst-v2.c: New.
> * gcc.target/powerpc/p8-vec-xl-xst.c: Disable gimple-folding.
> * gcc.target/powerpc/swaps-p8-17.c: Same.
Only one space after :
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86029
Tavian Barnes changed:
What|Removed |Added
CC||tavianator at gmail dot com
--- Comment
Thanks for pointing this out. I'll check out what's going on and fix the
issue
--Dave
On 05/31/2018 05:53 AM, H.J. Lu wrote:
On Wed, May 30, 2018 at 3:56 PM, Jeff Law wrote:
On 04/22/2018 01:17 PM, dave.pa...@oracle.com wrote:
This patch fixes handling of -Werror=return-type as well as
> On Jun 1, 2018, at 5:04 PM, Joseph Myers wrote:
>
> On Tue, 29 May 2018, Paul Koning wrote:
>
>> +unsigned short udivmodhi4(unsigned short, unsigned short, int);
>
> libgcc should not have any such non-static functions in the user
> namespace; they should all start with __.
That too is
On Thu, May 31, 2018 at 02:58:11PM -0500, Will Schmidt wrote:
> 2018-05-31 Will Schmidt
>
> * gcc.target/powerpc/fold-vec-store-builtin_vec_xst-char.c: New.
> * gcc.target/powerpc/fold-vec-store-builtin_vec_xst-double.c: New.
> *
On Thu, May 31, 2018 at 02:58:29PM -0500, Will Schmidt wrote:
> 2018-05-31 Will Schmidt
>
> * gcc.target/powerpc/fold-vec-store-vec_vsx_st-char.c: New.
> * gcc.target/powerpc/fold-vec-store-vec_vsx_st-double.c: New.
> *
On Tue, 29 May 2018, Paul Koning wrote:
> +unsigned short udivmodhi4(unsigned short, unsigned short, int);
libgcc should not have any such non-static functions in the user
namespace; they should all start with __.
--
Joseph S. Myers
jos...@codesourcery.com
Hi,
while working on some bugs I noticed that in a few places in decl.c we
could do better in terms of locations within the current infrastructure,
some simple, straightforward improvements. I'm attaching below a tiny
first patch, more to follow, I hope.
For example, a function which could
On Thu, May 31, 2018 at 02:57:48PM -0500, Will Schmidt wrote:
> 2018-05-31 Will Schmidt
>
> * gcc.target/powerpc/fold-vec-load-vec_vsx_ld-char.c : New.
> * gcc.target/powerpc/fold-vec-load-vec_vsx_ld-double.c : New.
> * gcc.target/powerpc/fold-vec-load-vec_vsx_ld-float.c
On Thu, May 31, 2018 at 02:57:34PM -0500, Will Schmidt wrote:
> 2018-05-31 Will Schmidt
>
> * gcc.target/powerpc/fold-vec-load-builtin_vec_xl-char.c: New.
> * gcc.target/powerpc/fold-vec-load-builtin_vec_xl-double.c: New.
> *
On Thu, May 31, 2018 at 02:57:21PM -0500, Will Schmidt wrote:
> 2018-05-31 Will Schmidt
>
> * gcc.target/powerpc/fold-vec-load-vec_xl-char.c
> * gcc.target/powerpc/fold-vec-load-vec_xl-double.c
> * gcc.target/powerpc/fold-vec-load-vec_xl-float.c
> *
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58281
--- Comment #4 from Jason Merrill ---
Author: jason
Date: Fri Jun 1 20:49:33 2018
New Revision: 261085
URL: https://gcc.gnu.org/viewcvs?rev=261085=gcc=rev
Log:
PR c++/58281 - explicit instantiation of constexpr
* pt.c
On Mon, 28 May 2018, Christophe Lyon wrote:
> On 25/05/2018 18:32, Joseph Myers wrote:
> > On Fri, 25 May 2018, Christophe Lyon wrote:
> >
> > > In libtool.m4, we use uclinuxfdpiceabi in cases where ELF shared
> > > libraries support is required, as uclinux does not guarantee that.
> >
> > To
Since 5.2, GCC has deferred instantiation of constexpr functions until
the point that the definition is necessary for evaluating a
constant-expression. The resolution of core issue 1581 says that we
need to be a bit more eager about instantiation: we should instantiate
a constexpr function that
On 06/01/2018 05:48 AM, Richard Biener wrote:
On Wed, May 30, 2018 at 1:53 AM Andrew MacLeod wrote:
This allows queries for a range on an edge, on entry to a block, as an
operand on an specific statement, or to calculate the range of the
result of a statement. There are no prerequisites to
Added myself to write after approval list in MAINTAINERS.
Index: ChangeLog
===
--- ChangeLog (revision 261081)
+++ ChangeLog (revision 261082)
@@ -1,3 +1,7 @@
+2018-06-01 Jozef Lawrynowicz
+
+ * MAINTAINERS (write after
I'm wondering if there are other suggestions to make this patch acceptable.
As I mentioned previously, the initialization process needs to go through all
of the widening tables in order to initialize all FP types, so we can't just
arbitrarily eliminate IFmode from the widening table.
I could
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58281
Jason Merrill changed:
What|Removed |Added
CC||jason at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86030
Bug ID: 86030
Summary: specs file processing does not create response files
for input directories
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85816
--- Comment #2 from kargl at gcc dot gnu.org ---
Author: kargl
Date: Fri Jun 1 20:20:35 2018
New Revision: 261081
URL: https://gcc.gnu.org/viewcvs?rev=261081=gcc=rev
Log:
2018-06-01 Steven G. Kargl
PR fortran/85816
PR
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85975
--- Comment #4 from kargl at gcc dot gnu.org ---
Author: kargl
Date: Fri Jun 1 20:20:35 2018
New Revision: 261081
URL: https://gcc.gnu.org/viewcvs?rev=261081=gcc=rev
Log:
2018-06-01 Steven G. Kargl
PR fortran/85816
PR
Hi!
On Tue, May 29, 2018 at 08:54:47AM -0700, Carl Love wrote:
> 2018-05-29 Carl Love
> * gcc.target/powerpc/altivec-35.c (foo): Add builtin test vec_madds.
> * gcc.target/powerpc/builtins-3-p9.c (main): Add tests for
> vec_extract_fp32_from_shortl and
Hi,
I've updated my email address in MAINTAINERS file.
I don't have FSF copyright assignment record for am...@gcc.gnu.org but
will sort it out before next commit to GCC.
Thanks,
bin
--- trunk/ChangeLog 2018/06/01 18:46:23 261078
+++ trunk/ChangeLog 2018/06/01 19:53:31 261079
@@ -1,3 +1,7 @@
Hi Carl,
On Tue, May 29, 2018 at 08:37:01AM -0700, Carl Love wrote:
> * gcc.target/powerpc/builtins-3.c: Add tests
> test_sll_vuill_vuill_vuc,
Stray tab.
> +/* { dg-final { scan-assembler-times "vupklpx" 1 { target le } } } */
> +/* { dg-final { scan-assembler-times "vupklpx" 1 {
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85997
--- Comment #3 from joseph at codesourcery dot com ---
The requirements on array declarators apply before parameter arrays decay
to pointers; see DR#047 (which concerns the case of an incomplete element
type - not itself a constraint violation
> Just a general remark, the many non-functional but stylistic changes do not
> make the patch easier to review ;)
Sorry about that (in this case the ChangeLog is supposed to help a little).
> + /* If bit insertion is required, we use the source as an
> accumulator +into
On June 1, 2018 7:34:25 PM GMT+02:00, vineet singh
wrote:
>Hi,
>
>I want to know that whether GCC provides a pass that gives us "may
>alias"
>information and how we can access it?
>
>If yes, then is this may alias information available before and after
>each
>pass of GCC?
May alias info is
Hi,
I have pushed the changes to github
(https://github.com/hrisearch/gcc). Added a command line option for
specific dumps of variables and functions used in IL e.g.
-fdump-lto-list=foo will dump:
Call Graph:
foo/1 (foo)
Type: function
visibility: default
Regards,
Hrishikesh
On Tue, May 29,
On Fri, Jun 01, 2018 at 02:49:51PM -0400, Paul Koning wrote:
> Given that the starting insn had a post_inc in it, what would be a proper
> parallel... construct? If the post_inc only appears in one of the two
> mentions of the source operatnd, then the match_dup is going to fail. I
> suppose I
> On Jun 1, 2018, at 2:40 PM, Jakub Jelinek wrote:
>
> On Fri, Jun 01, 2018 at 02:35:41PM -0400, Paul Koning wrote:
>> during RTL pass: dse2
>> dump file: unwind-dw2-fde.c.288r.dse2
>> ../../../../gcc/libgcc/unwind-dw2-fde.c: In function ‘get_cie_encoding’:
>>
This patch changes the (C++) mangling of the 128-bit float types.
IBM long double ("double-double") is mangled as "g", as before, and
IEEE 128-bit long double is mangled as "u9__ieee128".
Bootstrapped and tested on powerpc64-linux {-m32,-m64} (Power7) and
on powerpc64le-linux (Power9). Also
On Fri, Jun 01, 2018 at 02:35:41PM -0400, Paul Koning wrote:
> during RTL pass: dse2
> dump file: unwind-dw2-fde.c.288r.dse2
> ../../../../gcc/libgcc/unwind-dw2-fde.c: In function ‘get_cie_encoding’:
> ../../../../gcc/libgcc/unwind-dw2-fde.c:342:1: internal compiler error: in
> cselib_record_set,
Gentlepeople,
I'm using Eric Botcazou's recipe #2 for the CCmode version of pdp11 -- where
most instructions step on the condition codes so the CC references are inserted
post-reload. As part of that, the compare-elim pass gets rid of compares that
are redundant given that the instruction
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85840
Jerry DeLisle changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85840
--- Comment #16 from Jerry DeLisle ---
Author: jvdelisle
Date: Fri Jun 1 18:34:09 2018
New Revision: 261077
URL: https://gcc.gnu.org/viewcvs?rev=261077=gcc=rev
Log:
2018-06-01 Jerry DeLisle
Backport from trunk.
PR
This patch improves maintainability of the rs6000 built-in functions by adding
a comment to describe the non-traditional implementation of the
__builtin_vec_vsx_ld and __builtin_vec_vsx_st functions, and by removing eight
redundant entries from the altivec_overloaded_builtins array.
Note, in
Hi,
I want to know that whether GCC provides a pass that gives us "may alias"
information and how we can access it?
If yes, then is this may alias information available before and after each
pass of GCC?
--
Regards
Vineet Singh
Master of Technology
Department of Computer Science & Technology
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63570
kargl at gcc dot gnu.org changed:
What|Removed |Added
Status|NEW |RESOLVED
On Fri, Jun 01, 2018 at 09:50:06AM +0300, Janne Blomqvist wrote:
> On Mon, May 28, 2018 at 8:06 PM, Steve Kargl <
> s...@troutmask.apl.washington.edu> wrote:
>
> > The attached patch implements the RANDOM_INIT intrinsic
> > subroutine specified in Fortran 2018. I have had this
> > patch in my
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63570
--- Comment #3 from kargl at gcc dot gnu.org ---
Author: kargl
Date: Fri Jun 1 17:05:02 2018
New Revision: 261075
URL: https://gcc.gnu.org/viewcvs?rev=261075=gcc=rev
Log:
2018-06-01 Steven G. Kargl
PR fortran/63570
* check.c
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85997
--- Comment #2 from Kari Nurmela ---
There is only one array in the program, "array", and that is not a variable
length array. The syntax in print_array doesn't take any position on the kind
of the array, only that there are at least "count"
On Fri, Jun 1, 2018 at 11:52 AM, Marek Polacek wrote:
> On Thu, May 31, 2018 at 10:11:27AM -0400, Jason Merrill wrote:
>> On Wed, May 30, 2018 at 5:23 PM, Marek Polacek wrote:
>> > We are failing to deduce the template parameter N here
>> >
>> > template
>> > void foo(const long int (&)[N])
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86015
--- Comment #4 from Josh Marshall ---
These changes may make the stdlib implementation more robust, but there may be
an argument to stick to the more strict standard or tweak the standard. Could
you link to the standard doc you're pulling from?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86029
Bug ID: 86029
Summary: gcc -O3 make very slow product
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85997
--- Comment #1 from joseph at codesourcery dot com ---
Well, that's a VLA before the decay to pointer type, and thus violates the
C90 constraint referenced in the diagnostic. So a diagnostic is obviously
required with -std=c90 -pedantic or
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86028
Bug ID: 86028
Summary: Dead stores created by va_start/va_arg are not fully
cleaned up
Product: gcc
Version: 8.1.0
Status: UNCONFIRMED
Severity: minor
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85995
--- Comment #3 from joseph at codesourcery dot com ---
See trouble.texi, "Non-bugs" / "Certain Changes We Don't Want to Make",
"Undefining @code{__STDC__} when @option{-ansi} is not used." (and the
description of handling of base standards in
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86005
--- Comment #7 from James Y Knight ---
(In reply to Jim Wilson from comment #6)
> On Thu, 2018-05-31 at 15:07 +, foom at fuhm dot net wrote:
> > (But also, why doesn't it implement __atomic_add_fetch inline?)
>
> If you don't have atomic
On Thu, May 31, 2018 at 10:11:27AM -0400, Jason Merrill wrote:
> On Wed, May 30, 2018 at 5:23 PM, Marek Polacek wrote:
> > We are failing to deduce the template parameter N here
> >
> > template
> > void foo(const long int (&)[N]) {}
> >
> > void bar() {
> > foo ({1,2,3});
> > }
> >
Hi all,
The SSHL and USHL instructions are used with a shift operand of zero to
sign and zero-extend integer vectors into wider modes.
GCC makes extensive use of them to "unpack" vectors.
AArch64 defines a shorthand alias for that case. Instead of writing:
SSHLL ., ., 0
we can write
SXTL ., .
On Jun 1, 2018, at 10:35 AM, Richard Biener wrote:
>
> On June 1, 2018 5:15:58 PM GMT+02:00, Bill Schmidt
> wrote:
>> On Jun 1, 2018, at 10:11 AM, Will Schmidt
>> wrote:
>>>
>>> On Fri, 2018-06-01 at 08:53 +0200, Richard Biener wrote:
On Thu, May 31, 2018 at 9:59 PM Will Schmidt
>>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86026
--- Comment #3 from Alexander Monakov ---
Tree optimizations already manage to avoid "optimizing" f_intadd, but
unfortunately on RTL types and casts are not visible in IR and various passes
make no distinction between (char*)((uintptr_t)t + o)
On June 1, 2018 5:15:58 PM GMT+02:00, Bill Schmidt
wrote:
>On Jun 1, 2018, at 10:11 AM, Will Schmidt
>wrote:
>>
>> On Fri, 2018-06-01 at 08:53 +0200, Richard Biener wrote:
>>> On Thu, May 31, 2018 at 9:59 PM Will Schmidt
> wrote:
Hi,
Add support for gimple folding for
Hello,
I'd like to contribute a patch to GCC, and was told I need to get and sign a
copyright assignment form before I can do so. Could you send me the form - and
if there's a separate form needed for any release of copyright by my employer
(as the patch was developed as part of my job) I
On June 1, 2018 3:40:15 PM GMT+02:00, David Malcolm wrote:
>On Fri, 2018-06-01 at 11:50 +0200, Richard Biener wrote:
>> On Tue, May 29, 2018 at 10:33 PM David Malcolm
>> wrote:
>> >
>> > This was an experiment to try to capture information on a
>> > loop optimization.
>> >
>> > gcc/ChangeLog:
Hi!
I've noticed a lot of spots where we weren't using exact location, even when
we have OMP_CLAUSE_LOCATION we can use.
Fixed thusly, committed to gomp-5_0-branch.
2018-06-01 Jakub Jelinek
* c-typeck.c (c_finish_omp_clauses): Use error_at with
OMP_CLAUSE_LOCATION (c) as
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86027
Bug ID: 86027
Summary: string literals get corrupted with -O3 and gas on
solaris i386
Product: gcc
Version: 7.3.0
Status: UNCONFIRMED
Severity: normal
On Jun 1, 2018, at 10:11 AM, Will Schmidt wrote:
>
> On Fri, 2018-06-01 at 08:53 +0200, Richard Biener wrote:
>> On Thu, May 31, 2018 at 9:59 PM Will Schmidt
>> wrote:
>>>
>>> Hi,
>>> Add support for gimple folding for unaligned vector loads and stores.
>>> testcases posted separately in
On Fri, 2018-06-01 at 08:53 +0200, Richard Biener wrote:
> On Thu, May 31, 2018 at 9:59 PM Will Schmidt
> wrote:
> >
> > Hi,
> > Add support for gimple folding for unaligned vector loads and stores.
> > testcases posted separately in this thread.
> >
> > Regtest completed across variety of
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78870
Christophe Lyon changed:
What|Removed |Added
CC||clyon at gcc dot gnu.org
--- Comment
Hi,
I've updated my email address in the MAINTAINERS file.
Thanks,
- Tom
[MAINTAINERS] Update email address
2018-06-01 Tom de Vries
* MAINTAINERS: Update my email address.
---
MAINTAINERS | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/MAINTAINERS
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85964
Jeffrey A. Law changed:
What|Removed |Added
CC||law at redhat dot com
--- Comment #13
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86026
--- Comment #2 from Pascal Cuoq ---
Created attachment 44223
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=44223=edit
Complete source code for functions in the description
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86025
Jakub Jelinek changed:
What|Removed |Added
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed|
On Fri, Jun 01, 2018 at 03:43:38PM +0200, Thomas Schwinge wrote:
> > +STAGE1_TFLAGS += -fno-checking
> > +STAGE2_CFLAGS += -fno-checking
> > +STAGE2_TFLAGS += -fno-checking
> > +STAGE3_CFLAGS += -fchecking
> > +STAGE3_TFLAGS += -fchecking
>
> This however means that when a user configured with
Hi!
On Thu, 26 Apr 2018 10:08:09 +0200 (CEST), Richard Biener
wrote:
> --- Makefile.tpl (revision 259638)
> +++ Makefile.tpl (working copy)
> @@ -452,11 +452,21 @@ STAGE1_CONFIGURE_FLAGS = --disable-inter
> --disable-coverage --enable-languages="$(STAGE1_LANGUAGES)" \
>
Hi!
On Wed, 11 Apr 2018 20:55:49 +0200, Jakub Jelinek wrote:
> On Wed, Apr 11, 2018 at 06:07:17PM +0200, Matthias Klose wrote:
> > On 11.04.2018 12:31, Jakub Jelinek wrote:
> > > As discussed, using --as-needed and --no-as-needed is dangerous, because
> > > it results in --no-as-needed even for
On Fri, 2018-06-01 at 11:50 +0200, Richard Biener wrote:
> On Tue, May 29, 2018 at 10:33 PM David Malcolm
> wrote:
> >
> > This was an experiment to try to capture information on a
> > loop optimization.
> >
> > gcc/ChangeLog:
> > * gimple-loop-interchange.cc (should_interchange_loops):
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85958
--- Comment #6 from Jonny Grant ---
Clang shows:
$ clang -o main main.cpp -Wall -Werror -Wconversion
main.cpp:15:5: error: no matching function for call to 'strstripspace'
strstripspace(unused, two);
^
main.cpp:5:6: note:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85958
--- Comment #5 from Jonny Grant ---
(In reply to Tavian Barnes from comment #4)
> IMHO "discards qualifiers" and even "discards const qualifier" are still
> confusing. Making it clearly counterfactual, as in "...would discard
> (const)
1 - 100 of 174 matches
Mail list logo
