https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66159
--- Comment #4 from Eric Gallager ---
(In reply to Jonathan Wakely from comment #3)
> Patch for stage 1:
>
> diff --git a/gcc/cp/parser.c b/gcc/cp/parser.c
> index 4fa546a086c..4dc4e751b28 100644
> --- a/gcc/cp/parser.c
> +++ b/gcc/cp/parser.c
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86021
Bug ID: 86021
Summary: ICE when initializing a character array
Product: gcc
Version: 7.2.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: fortran
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85840
--- Comment #15 from Jerry DeLisle ---
Author: jvdelisle
Date: Fri Jun 1 02:14:53 2018
New Revision: 261054
URL: https://gcc.gnu.org/viewcvs?rev=261054=gcc=rev
Log:
2018-05-31 Jerry DeLisle
Backport from trunk.
PR
Hi Richard,
This is the revised patch based on the review and the discussion in
https://gcc.gnu.org/ml/gcc/2018-05/msg00179.html.
In summary:
- I skipped (element_precision (type) < element_precision (TREE_TYPE
(@0))) in the match.pd pattern as this would prevent transformation
for the case in
On Sat, 26 May 2018, Will Hawkins wrote:
> > + if (asmspec_tree != NULL_TREE)
> > +{
> > + warning (OPT_Wignored_asm_name, "asm-specifier is ignored in "
> > + "typedef declaration");
> > +}
We avoid braces around a single statement like this.
I don't think
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85957
--- Comment #11 from joseph at codesourcery dot com ---
On Mon, 28 May 2018, vincent-gcc at vinc17 dot net wrote:
> floating-point expression: Once a floating-point number has been converted
> into
> an integer type, the value of this integer
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85429
--- Comment #12 from ian at gcc dot gnu.org ---
Author: ian
Date: Thu May 31 22:46:52 2018
New Revision: 261045
URL: https://gcc.gnu.org/viewcvs?rev=261045=gcc=rev
Log:
PR go/85429
Various backports from mainline:
libgo: update to
I've committed this patch to update the GCC 8 branch to the Go 1.10.2
release, and also brought along a couple of other recent fixes.
Bootstrapped and ran Go testsuite on x86_64-pc-linux-gnu. Committed
to mainline.
cmd/go: support more Solaris assembler syntaxes
Patch by Rainer Orth.
Snapshot gcc-7-20180531 is now available on
ftp://gcc.gnu.org/pub/gcc/snapshots/7-20180531/
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=85984
Jakub Jelinek changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85950
Uroš Bizjak changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85591
Uroš Bizjak changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85950
--- Comment #8 from uros at gcc dot gnu.org ---
Author: uros
Date: Thu May 31 22:09:39 2018
New Revision: 261043
URL: https://gcc.gnu.org/viewcvs?rev=261043=gcc=rev
Log:
PR target/85950
* config/i386/i386.md (l2):
Enable
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85591
--- Comment #5 from uros at gcc dot gnu.org ---
Author: uros
Date: Thu May 31 22:04:22 2018
New Revision: 261042
URL: https://gcc.gnu.org/viewcvs?rev=261042=gcc=rev
Log:
PR target/85591
* config/i386/cpuinfo.c (get_amd_cpu):
On May 30, 2018, at 3:41 AM, Tom de Vries wrote:
>
> this patch tests the error behaviour of dg-final directives when called with
> an
> incorrect number of arguments.
Seems reasonable. Unless someone wanted to argue against it for some reason
(not portable, takes too much time, hard to
This patch to libgo updates it to the 1.10.2 release. Bootstrapped
and ran Go testsuite on x86_64-pc-linux-gnu. Committed to mainline.
Ian
Index: gcc/go/gofrontend/MERGE
===
--- gcc/go/gofrontend/MERGE (revision 260913)
+++
With that in place, please go ahead and start filling this.
For GCC 8 many items came late, and I'm sure that we are still
missing many that would have been worth documenting here.
Gerald
Applied as follows...
Index: changes.html
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78809
qinzhao at gcc dot gnu.org changed:
What|Removed |Added
CC||qinzhao at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83819
Bug 83819 depends on bug 83026, which changed state.
Bug 83026 Summary: missing strlen optimization for strcmp of unequal strings
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83026
What|Removed |Added
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83026
qinzhao at gcc dot gnu.org changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83026
qinzhao at gcc dot gnu.org changed:
What|Removed |Added
CC||qinzhao at gcc dot gnu.org
Hi,
I have committed the patch as revision 261039.
thanks.
Qing
> On May 29, 2018, at 7:08 PM, Qing Zhao wrote:
>
> Hi, Jeff,
>
> Thanks a lot for your review and comments.
>
> I have updated my patch based on your suggestion, and retested this whole
> patch on both X86 and aarch64.
>
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86005
--- Comment #6 from Jim Wilson ---
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 instructions, then we call an out-of-line
function that
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86020
Bill Schmidt changed:
What|Removed |Added
Keywords||missed-optimization
Target|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86020
--- Comment #1 from Bill Schmidt ---
Created attachment 44220
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=44220=edit
Source file that shows the problem
Hi,
Enable some variations of the _builtin_vec_xst() instrinsic.
For most data types (char,short,int,...) the _builtin_vec_xst() intrinsic
accepts either a pointer to , or a pointer to a vector of elements of
. We currently do not accept pointer-to-type for the long long or
double data types.
Hi,
Add support for gimple folding for unaligned vector loads and stores.
testcases posted separately in this thread.
Regtest completed across variety of systems, P6,P7,P8,P9.
OK for trunk?
Thanks,
-Will
[gcc]
2018-05-31 Will Schmidt
* config/rs6000/rs6000.c:
Hi,
Testcase coverage for variations of the vec_xst() intrinsic.
Regtest clean across assorted Linux systems (p6-p9).
OK for trunk?
Thanks,
-Will
[testsuite]
2018-05-31 Will Schmidt
* gcc.target/powerpc/fold-vec-store-vec_xst-char.c : New.
*
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86020
Bug ID: 86020
Summary: Performance regression in Eigen geometry.cpp test
starting with r248333
Product: gcc
Version: 8.1.0
Status: UNCONFIRMED
Severity: normal
Hi,
Assorted updates to existing tests to compensate for codegen changes
introduced with the gimple-folding of unaligned vector loads and stores.
Regtest clean across assorted Linux systems (p6-p9).
OK for trunk?
Thanks,
-Will
[testsuite]
2018-05-31 Will Schmidt
*
Hi,
New testcases to cover variations of the vec_vsx_st() intrinsic.
Regtest clean across assorted Linux systems (p6-p9).
OK for trunk?
Thanks,
-Will
[testsuite]
2018-05-31 Will Schmidt
* gcc.target/powerpc/fold-vec-store-vec_vsx_st-char.c: New.
*
Hi,
Add testcase coverage for variations of the builtin_vec_xst() intrinsic.
Regtest clean across assorted Linux systems (p6-p9).
OK for trunk?
Thanks,
-Will
[testsuite]
2018-05-31 Will Schmidt
* gcc.target/powerpc/fold-vec-store-builtin_vec_xst-char.c: New.
*
Hi,
Add testcase coverage for variations of the vec_vsx_ld() intrinsic.
Regtest clean across assorted Linux systems (p6-p9).
OK for trunk?
Thanks,
-Will
[testsuite]
2018-05-31 Will Schmidt
* gcc.target/powerpc/fold-vec-load-vec_vsx_ld-char.c : New.
*
Hi,
Add testcase coverage for variations of the builtin_vec_xl() intrinsic.
Regtest clean across assorted Linux systems (p6-p9).
OK for trunk?
Thanks,
-Will
[testsuite]
2018-05-31 Will Schmidt
* gcc.target/powerpc/fold-vec-load-builtin_vec_xl-char.c: New.
*
Hi,
Add testcase coverage for variations of the vec_xl() intrinsic.
Regtest clean across assorted Linux systems (p6-p9).
OK for trunk?
Thanks,
-Will
[testsuite]
2018-05-31 Will Schmidt
* gcc.target/powerpc/fold-vec-load-vec_xl-char.c
*
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66193
kargl at gcc dot gnu.org changed:
What|Removed |Added
CC||kargl at gcc dot gnu.org
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85984
--- Comment #6 from Jakub Jelinek ---
Author: jakub
Date: Thu May 31 19:51:50 2018
New Revision: 261038
URL: https://gcc.gnu.org/viewcvs?rev=261038=gcc=rev
Log:
PR target/85984
* bb-reorder.c (pass_partition_blocks::gate):
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85984
--- Comment #5 from Jakub Jelinek ---
Author: jakub
Date: Thu May 31 19:49:54 2018
New Revision: 261037
URL: https://gcc.gnu.org/viewcvs?rev=261037=gcc=rev
Log:
PR target/85984
* bb-reorder.c (pass_partition_blocks::gate):
Hello!
As reported in the PR, AMDFAM15H model 0x2 should return
AMDFAM15H_BDVER2 subtype.
2018-05-31 Uros Bizjak
PR target/85591
* config/i386/cpuinfo.c (get_amd_cpu): Return
AMDFAM15H_BDVER2 for AMDFAM15H model 0x2.
Bootstrapped and regression tested on x86_64-linux-gnu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85591
--- Comment #4 from uros at gcc dot gnu.org ---
Author: uros
Date: Thu May 31 19:45:54 2018
New Revision: 261036
URL: https://gcc.gnu.org/viewcvs?rev=261036=gcc=rev
Log:
PR target/85591
* config/i386/cpuinfo.c (get_amd_cpu):
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78870
--- Comment #15 from Jonathan Wakely ---
P.S. thanks to niXman for the patch that inspired the approach used.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78870
Jonathan Wakely changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85670
--- Comment #6 from Jonathan Wakely ---
Fixed on trunk now. See PR 78870.
On Thu, May 31, 2018 at 7:23 AM, Matthew Fortune
wrote:
> I do actually have a solution for this but it is not submitted upstream.
> MIPS has basically the same set of problems that RISC-V does in this area
> and in an ideal world there would be no 'fallback' multilib such that if
> you use
Hi,
I've broken this set of patches up into bite-sized chunks for easier
review and management. They'll be showing up as replies to this
message.
#1-6 are straightforward tests to cover the variations of the vector
load and store intrinsics. These look much alike, but there really are
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78870
--- Comment #13 from Jonathan Wakely ---
Author: redi
Date: Thu May 31 19:20:24 2018
New Revision: 261034
URL: https://gcc.gnu.org/viewcvs?rev=261034=gcc=rev
Log:
PR libstdc++/78870 support std::filesystem on Windows
PR libstdc++/78870
On Wed, May 30, 2018 at 06:43:23PM +0200, Jakub Jelinek wrote:
> On Wed, May 30, 2018 at 08:45:22AM -0500, Segher Boessenkool wrote:
> > > If you need to keep g for compatibility (you do), then why not just have
> > > e (long double is double)
> > > g (long double when matching __ibm128, or
This adds incomplete but functional support for std::filesystem and
std::experimental::filesystem on MinGW. In theory there should be no
changes to the existing behaviour for POSIX targets from this patch,
as all the various bugs I found while working on this have already
been fixed in separate
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86015
Jonathan Wakely changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
On Thu, 24 May 2018, Jeff Law wrote:
> > I can try to fix openbsd soon, but freebsd dropped alpha in 2009.
> > How does gcc feel about me picking up patches from openbsd ports, their
> > package manager, that weren't written by myself?
> So ISTM we should deprecate freebsd alpha.
Ab-so-lutely.
> On May 31, 2018, at 12:35 PM, Joseph Myers wrote:
>
> On Tue, 29 May 2018, Paul Koning wrote:
>
>> Question about proper target maintainer procedures...
>>
>> The pdp11 target needs udivhi3 in libgcc. There's udivsi3, and it's
>> really easy to tweak those files for HImode. And that
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86019
Andrew Pinski changed:
What|Removed |Added
Target||x86_64
URL|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86019
Bug ID: 86019
Summary: Unref implementation using atomic_thread_fence
generates worse code on x86-64 in gcc 8.1 than 7.3
Product: gcc
Version: unknown
Status:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86018
Bug ID: 86018
Summary: Incorrect unused warning for int passed by reference
to lambda
Product: gcc
Version: 8.1.0
Status: UNCONFIRMED
Severity: normal
No functional changes.
2018-05-31 Uros Bizjak
* config/i386/sse.md (avx_vec_concat):
Substitute concat_tg_mode mode attribute with xtg_mode.
(avx512dq_broadcast_1): Ditto.
(concat_tg_mode): Remove mode attribute.
Bootstrapped and regression tested on x86_64-linux-gnu.
On Thu, May 31, 2018 at 3:51 AM, Kugan Vivekanandarajah
wrote:
> Hi Bin,
>
> Thanks for the review. Please find the revised patch based on the
> review comments.
>
> Thanks,
> Kugan
>
> On 17 May 2018 at 19:56, Bin.Cheng wrote:
>> On Thu, May 17, 2018 at 2:39 AM, Kugan Vivekanandarajah
>>
On Thu, May 31, 2018 at 01:34:19PM -0400, Jason Merrill wrote:
> >> Where is the error_mark_node coming from in the first place?
> >
> > remap_type invoked during omp-low.c (scan_omp).
> > omp_copy_decl returns error_mark_node for decls that tree-inline.c wants
> > to remap, but they aren't
On Thu, May 31, 2018 at 11:31 AM, Jakub Jelinek wrote:
> On Thu, May 31, 2018 at 11:19:08AM -0400, Jason Merrill wrote:
>> > In my mind the issue boils down to two questions:
>> >
>> > 1) should the pretty printer handle error-mark-node gracefully
>> >or is it appropriate for it to abort?
>>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86015
--- Comment #2 from Josh Marshall ---
There are also lines close by which call std::distance() which need to be
similarly wrapped.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85931
Martin Sebor changed:
What|Removed |Added
Keywords||patch
--- Comment #3 from Martin Sebor
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86017
Martin Sebor changed:
What|Removed |Added
Keywords||missed-optimization
See Also|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86017
Bug ID: 86017
Summary: multiple consecutive calls to bzero/memset not merged
Product: gcc
Version: 8.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Hi!
I've committed following patch to gomp-5_0-branch, which:
1) adds support for memory-order clauses other than seq_cst to atomic
construct
2) adds support for hint clause on atomic construct, fixes some hint related
glitches on critical construct; hints are ignored aftere checking their
On 05/30/2018 05:18 PM, Jeff Law wrote:
On 05/18/2018 05:58 PM, Martin Sebor wrote:
The -Walloc-size-larger-than= option is supposed make it possible
to disable the warning by specifying a limit that's larger than
the default of PTRDIFF_MAX (the handler for the option argument
gets around the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82063
--- Comment #8 from Martin Sebor ---
Author: msebor
Date: Thu May 31 17:04:43 2018
New Revision: 261030
URL: https://gcc.gnu.org/viewcvs?rev=261030=gcc=rev
Log:
PR c/82063 - issues with arguments enabled by -Wall
gcc/c-family/ChangeLog:
On Tue, 29 May 2018, Paul Koning wrote:
> Question about proper target maintainer procedures...
>
> The pdp11 target needs udivhi3 in libgcc. There's udivsi3, and it's
> really easy to tweak those files for HImode. And that works.
>
> Should I add the HI files to the libgcc directory, or
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86016
Bug ID: 86016
Summary: New tests for r260978 report excess errors
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component:
On Tue, 29 May 2018, Richard Biener wrote:
> The testcase dates back to some repository creation rev. (egcs?) and
> I'm not sure we may compute the difference of addresses of structure
> members. So that GCC accepts this is probably not required. Joseph
> may have a definitive answer here.
My
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68791
--- Comment #7 from David Binderman ---
This bug seems to have been present since some revision before 260047.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86015
--- Comment #1 from Josh Marshall ---
It looks like wrappings would be applicable at the following lines:
296, 297, 2438, 2439, 2494, 2495
using
https://github.com/gcc-mirror/gcc/blob/master/libstdc%2B%2B-v3/include/bits/stl_algo.h
as
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68791
--- Comment #6 from David Binderman ---
Created attachment 44219
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=44219=edit
x86_64 object module
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68791
David Binderman changed:
What|Removed |Added
CC||dcb314 at hotmail dot com
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85993
Oleg Endo changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85829
H.J. Lu changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86015
Bug ID: 86015
Summary: Better handling of iterator distances
Product: gcc
Version: 7.3.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85829
--- Comment #7 from hjl at gcc dot gnu.org ---
Author: hjl
Date: Thu May 31 15:37:22 2018
New Revision: 261028
URL: https://gcc.gnu.org/viewcvs?rev=261028=gcc=rev
Log:
x86: Re-enable partial_reg_dependency and movx for Haswell
r254152 disabled
On Thu, May 31, 2018 at 8:08 AM, Jan Hubicka wrote:
>>
>> This is the patch I am going to check into GCC 8.
>>
>> --
>> H.J.
>
>> From 9ecbfa1fd04dc4370a9ec4f3d56189cc07aee668 Mon Sep 17 00:00:00 2001
>> From: "H.J. Lu"
>> Date: Thu, 17 May 2018 09:52:09 -0700
>> Subject: [PATCH] x86: Re-enable
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86005
Jim Wilson changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
On Thu, May 31, 2018 at 11:19:08AM -0400, Jason Merrill wrote:
> > In my mind the issue boils down to two questions:
> >
> > 1) should the pretty printer handle error-mark-node gracefully
> >or is it appropriate for it to abort?
> > 2) is it appropriate to be embedding/using error_mark_node in
On Thu, May 31, 2018 at 11:00 AM, Martin Sebor wrote:
> On 05/31/2018 07:30 AM, Jakub Jelinek wrote:
>>
>> On Thu, May 31, 2018 at 09:14:33AM -0400, Jason Merrill wrote:
I came up with the following hack instead (or in addition to),
replace those error_mark_node bounds with NULL
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86005
--- Comment #5 from Jim Wilson ---
On Thu, 2018-05-31 at 05:40 +, asb at lowrisc dot org wrote:
> Actually I think this bug is wider in scope than I first thought. GCC
> will also
> intermix __atomic libcalls and inline instruction sequences
>
> This is the patch I am going to check into GCC 8.
>
> --
> H.J.
> From 9ecbfa1fd04dc4370a9ec4f3d56189cc07aee668 Mon Sep 17 00:00:00 2001
> From: "H.J. Lu"
> Date: Thu, 17 May 2018 09:52:09 -0700
> Subject: [PATCH] x86: Re-enable partial_reg_dependency and movx for Haswell
>
> r254152
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86005
James Y Knight changed:
What|Removed |Added
CC||foom at fuhm dot net
--- Comment #4
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85829
--- Comment #5 from Sebastian Peryt ---
I have made measurements on HSW comparing
-mtune-ctrl=movx,partial_reg_dependency -Ofast -march=haswell to -Ofast
-mtune=haswell and I see improvements on EEMBC benchmarks.
automotive
=
aifftr01
On 05/31/2018 07:30 AM, Jakub Jelinek wrote:
On Thu, May 31, 2018 at 09:14:33AM -0400, Jason Merrill wrote:
I came up with the following hack instead (or in addition to),
replace those error_mark_node bounds with NULL (i.e. pretend flexible array
members) if during OpenMP/OpenACC outlining
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86000
--- Comment #2 from Hubert Matthews ---
template
int f()
{
bool check = requires { 3 > 4; };
if (check) return 1;
else return 2;
}
compiles cleanly and gives the expected result. This is essentially the same
code but with the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86000
--- Comment #1 from Hubert Matthews ---
template
int f()
{
bool check = requires { 3 > 4; };
if (check) return 1;
else return 2;
}
compiles cleanly and gives the expected result. This is essentially the same
code but with the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86004
--- Comment #3 from seurer at gcc dot gnu.org ---
I tried a couple of different versions of binutils on one system where this was
occurring and it happens with binutils 2.26 but doesn't with 2.27 (and later).
On Wed, May 30, 2018 at 5:43 AM, H.J. Lu wrote:
> On Sun, May 20, 2018 at 11:51 AM, Jan Hubicka wrote:
>>> r254152 disabled partial_reg_dependency and movx for Haswell and newer
>>> Intel processors. r258972 restored them for skylake-avx512. For Haswell,
>>> movx improves performance. But
Palmer Dabbelt writes:
> On Tue, 29 May 2018 11:02:58 PDT (-0700), Jim Wilson wrote:
> > On 05/26/2018 06:04 AM, Sebastian Huber wrote:
> >> Why is the default multilib and a variant identical?
> >
> > This is supposed to be a single multilib, with two names. We use
> > MULTILIB_REUSE to map the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86004
--- Comment #2 from seurer at gcc dot gnu.org ---
Sorry about that. The actual complaints are about a missing plugin from the
loader. I've never seen anything like that before.
gcc/testsuite/gfortran/gfortran.log:/usr/bin/ld:
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});
> }
>
> because of the type mismatch; parm is long int (element type of the array),
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85951
--- Comment #4 from Jonathan Wakely ---
Fixed for trunk and 8.2 so far.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85879
--- Comment #4 from cesar at gcc dot gnu.org ---
Author: cesar
Date: Thu May 31 14:10:10 2018
New Revision: 261025
URL: https://gcc.gnu.org/viewcvs?rev=261025=gcc=rev
Log:
Fix PR middle-end/85879
gcc/
* gimplify.c
On 31/05/18 13:17 +0100, Jonathan Wakely wrote:
Because the wide character types are neither signed integer types nor
unsigned integer types they need to be transformed to an integral type
of the correct size and the lowest rank (which is not necessarily the
underlying type). Reuse the helpers
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85951
--- Comment #3 from Jonathan Wakely ---
Author: redi
Date: Thu May 31 14:07:22 2018
New Revision: 261024
URL: https://gcc.gnu.org/viewcvs?rev=261024=gcc=rev
Log:
PR libstdc++/85951 for make_signed/make_unsigned for character types
Because the
On Thu, May 31, 2018 at 06:54:11AM -0700, Cesar Philippidis wrote:
> 2018-05-31 Chung-Lin Tang
> Cesar Philippidis
>
> PR middle-end/85879
>
> gcc/
> * gimplify.c (gimplify_adjust_omp_clauses): Add 'remove = true'
> when emitting error on
OpenACC has slightly different data semantics for reference types and
pointers. Without this patch, omp-low was treating all references types
like pointers which resulted in some gimple type checking errors when
checking is enabled. It turned out that Chung-Lin had resolved the issue
way back in
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85670
--- Comment #5 from Jonathan Wakely ---
All those issues will be fixed later today.
On May 31, 2018 12:02:49 PM GMT+02:00, Jakub Jelinek wrote:
>On Thu, May 31, 2018 at 11:46:33AM +0200, Richard Biener wrote:
>> Is naked an attribute that is specified for all targets? If so, OK.
>
>It is not specified for all targets, but all targets for which it is
>specified have the same
1 - 100 of 159 matches
Mail list logo
