https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80258
John Ousterhout changed:
What|Removed |Added
CC||ouster at cs dot stanford.edu
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60818
--- Comment #19 from Alan Modra ---
Yes, r246294 powerpc64le-linux-gcc -O1 -misel ICEs on the last testcase. An
earlier compiler I had laying around, 7.0.0 20160616, does not.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80257
--- Comment #3 from nightstrike ---
$ ./test.exe
Program received signal SIGSEGV: Segmentation fault - invalid memory reference.
Backtrace for this error:
#0 0x in ???
#1 0x in ???
#2 0x in
On 03/31/17 01:27, Nathan Sidwell wrote:
> On 03/30/2017 04:11 PM, Bernd Edlinger wrote:
>> Hi,
>>
>> I'd like to fix a few buffer overruns I have found in the gcov tools.
>> First I noticed that the -x output contains most of the time "ff" bytes,
>> and that when different source files exist in
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80267
Jonathan Wakely changed:
What|Removed |Added
Keywords||ice-on-valid-code
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=26461
John Ousterhout changed:
What|Removed |Added
CC||ouster at cs dot stanford.edu
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80268
Bug ID: 80268
Summary: [concepts] list of candidates for ambiguous call
includes unconstrained function
Product: gcc
Version: 7.0.1
Status: UNCONFIRMED
Minor patch to had translation marks.
Regression tested. OK for Trunk?
Jerry
2017-03-30 Jerry DeLisle
PR fortran/38573
* intrinsic.c (gfc_check_intrinsic_standard): Adjust diagnostics.
diff --git a/gcc/fortran/intrinsic.c b/gcc/fortran/intrinsic.c
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=43496
Segher Boessenkool changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80134
Segher Boessenkool changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67288
--- Comment #7 from Segher Boessenkool ---
*** Bug 80134 has been marked as a duplicate of this bug. ***
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80132
Segher Boessenkool changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80056
Segher Boessenkool changed:
What|Removed |Added
Status|NEW |RESOLVED
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=17593
Segher Boessenkool changed:
What|Removed |Added
Status|NEW |RESOLVED
CC|
On 03/30/2017 04:11 PM, Bernd Edlinger wrote:
Hi,
I'd like to fix a few buffer overruns I have found in the gcov tools.
First I noticed that the -x output contains most of the time "ff" bytes,
and that when different source files exist in different directories,
with same base name the MD5 sum
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80267
Bug ID: 80267
Summary: Compiling aborts when template/auto/lambda occur in
some way
Product: gcc
Version: 7.0.1
Status: UNCONFIRMED
Severity: normal
On 03/30/2017 05:50 PM, Daniel Santos wrote:
> I have finally completed all tests for Cygwin and MinGW both 32- &
> 64-bit with no additional test failures. There are still 567 tests
> failing both pre- and post-patch with error "error while loading shared
> libraries: cyggfortran-4.dll: cannot
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=27212
Segher Boessenkool changed:
What|Removed |Added
Status|NEW |RESOLVED
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80258
--- Comment #9 from Tor Myklebust ---
OK, I gather that the gcc developers, as a group, are against changing this
behaviour. (I can speculate why; almost all code that uses TLS will see a
slowdown.)
In order to work around this behaviour, one
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=20614
Segher Boessenkool changed:
What|Removed |Added
Status|NEW |RESOLVED
CC|
This is a fix for a compile failure in gcc.c-torture/compile/pr70240.c
with options -O1 -mmsa.
The expand code for replicated constant vectors with small immediate
values was simply wrong and would never work. This code is not used in the
simple case of initialising a variable with a constant
Snapshot gcc-6-20170330 is now available on
ftp://gcc.gnu.org/pub/gcc/snapshots/6-20170330/
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
pr52125.c verifies that orphaned %hi relocs are deleted if they feed
an inline asm statement that never emits the %lo part. Orphaned %hi
relocs are only strictly a problem for o32 but are eliminated for
any ABI as long as 32-bit addressing is in use so force -msym32 as well
as require absolute
On 03/30/2017 02:24 PM, Jakub Jelinek wrote:
On Thu, Mar 30, 2017 at 10:21:09AM -0600, Martin Sebor wrote:
I don't think rejecting all VLA initialization just to avoid
an Asan ICE with string literals is a good way to solve the
problem. For one, it will break working programs that rely on
Hi!
On some arches like x86_64 we allow some aggregates in named register
variables. If those registers are wider than word, store_bit_field_1
was assuming it must be multiple registers and attempted to pick
a word sized subregister of it, which is fine for pseudos, but if the
destination is a
For gcc-4.0/ and faq.html I did adjust the link, for gcc-3.2/ I
figured we can as well avoid it.
Applied.
(Jonathan, I'm going to take care of the libstdc++/doc links as
well in case you wonder.)
Gerald
Index: faq.html
===
RCS
Hi!
As discussed with Jon, libstdc++ needs a GCC builtin in order to implement
this easily.
Bootstrapped/regtested on x86_64-linux and i686-linux, ok for trunk?
2017-03-30 Jakub Jelinek
PR libstdc++/80251
c-family/
* c-common.h (enum rid): Add
Hi!
This makes it clearer to translators and users that parallel, teams etc.
are keywords.
Bootstrapped/regtested on x86_64-linux and i686-linux, committed to trunk.
2017-03-30 Jakub Jelinek
PR translation/80189
* gimplify.c (omp_default_clause): Use %qs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80189
--- Comment #5 from Jakub Jelinek ---
Author: jakub
Date: Thu Mar 30 20:31:40 2017
New Revision: 246599
URL: https://gcc.gnu.org/viewcvs?rev=246599=gcc=rev
Log:
PR translation/80189
* gimplify.c (omp_default_clause): Use %qs
Hi!
We print an uninitialized variable if OMP_DISPLAY_ENV=true is
in the environment, but {,G}OMP_STACKSIZE is not.
Fixed thusly, bootstrapped/regtested on x86_64-linux and i686-linux,
committed to trunk.
2017-03-30 Jakub Jelinek
* env.c (initialize_env):
On Thu, Mar 30, 2017 at 10:21:09AM -0600, Martin Sebor wrote:
> I don't think rejecting all VLA initialization just to avoid
> an Asan ICE with string literals is a good way to solve the
> problem. For one, it will break working programs that rely on
The Asan ICE can be easily worked around, the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80246
Peter Bergner changed:
What|Removed |Added
Status|RESOLVED|CLOSED
--- Comment #7 from Peter
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80246
Peter Bergner changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
On 3/30/17 12:54 PM, Peter Bergner wrote:
> On 3/30/17 12:15 PM, Segher Boessenkool wrote:
> +/* { dg-final { scan-assembler-not "drintn\\." } } */
> +/* { dg-final { scan-assembler-not "drintnq\\." } } */
> +/* { dg-final { scan-assembler-not "dctfix" } } */
> +/* { dg-final {
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80246
--- Comment #5 from Peter Bergner ---
Author: bergner
Date: Thu Mar 30 20:09:32 2017
New Revision: 246596
URL: https://gcc.gnu.org/viewcvs?rev=246596=gcc=rev
Log:
gcc/
Backport from mainline
2017-03-30 Peter Bergner
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80246
--- Comment #4 from Peter Bergner ---
Author: bergner
Date: Thu Mar 30 20:06:06 2017
New Revision: 246595
URL: https://gcc.gnu.org/viewcvs?rev=246595=gcc=rev
Log:
gcc/
Backport from mainline
2017-03-30 Peter Bergner
Hi,
I'd like to fix a few buffer overruns I have found in the gcov tools.
First I noticed that the -x output contains most of the time "ff" bytes,
and that when different source files exist in different directories,
with same base name the MD5 sum always matches, which results in
gcov overwriting
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80246
--- Comment #3 from Peter Bergner ---
Author: bergner
Date: Thu Mar 30 19:57:20 2017
New Revision: 246594
URL: https://gcc.gnu.org/viewcvs?rev=246594=gcc=rev
Log:
gcc/
PR target/80246
* config/rs6000/dfp.md (dfp_dxex_): Update
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=49498
--- Comment #26 from Jeffrey A. Law ---
So I had hoped this old BZ would be fixed by the changes for 71437. Sadly,
that is not the case.
*But* the WIP for for 78496 does happen to fix this BZ. In fact, we only need
the hunks from 78496 which
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79929
--- Comment #3 from Harald Anlauf ---
I've slightly reduced the example to the following:
% cat gfcbug138c.f90
subroutine gfcbug138 (yerrmsg)
character(kind=1,len=*) :: yerrmsg
yerrmsg = 1_"bug: " // yerrmsg
end subroutine gfcbug138
The
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80046
--- Comment #5 from janus at gcc dot gnu.org ---
(In reply to janus from comment #4)
> I'm currently regtesting a draft patch ...
After regtesting completed successfully, it was posted for review here:
This fix is similar to c++/79653: if something went wrong during
make_pack_expansion, return error_mark instead of building up the attribute
otherwise we end up with "gnu aligned <<>>" and that would mean crashing
later on at a lot of spots.
Also, dump_expr wasn't able to print TREE_LISTs. It's
On 3/30/17 12:15 PM, Segher Boessenkool wrote:
+/* { dg-final { scan-assembler-not "drintn\\." } } */
+/* { dg-final { scan-assembler-not "drintnq\\." } } */
+/* { dg-final { scan-assembler-not "dctfix" } } */
+/* { dg-final { scan-assembler-not "dctfixq" } } */
>>>
>>> If
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79534
--- Comment #7 from James Greenhalgh ---
I'm not sure there are any bugs here to fix, though I can still reproduce the
performance differences.
First up, basic block reordering causes an issue across all microarchitectures
on which I've looked
I have finally completed all tests for Cygwin and MinGW both 32- &
64-bit with no additional test failures. There are still 567 tests
failing both pre- and post-patch with error "error while loading shared
libraries: cyggfortran-4.dll: cannot open shared object file: No such
file or
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80241
Marek Polacek changed:
What|Removed |Added
Status|NEW |ASSIGNED
CC|
> >> +/* { dg-final { scan-assembler-not "drintn\\." } } */
> >> +/* { dg-final { scan-assembler-not "drintnq\\." } } */
> >> +/* { dg-final { scan-assembler-not "dctfix" } } */
> >> +/* { dg-final { scan-assembler-not "dctfixq" } } */
> >
> > If there is no "dctfix" there surely is no "dctfixq"
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80233
--- Comment #9 from Segher Boessenkool ---
Yeah exactly... so I'm conflicted whether we need to backport this or not.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64883
--- Comment #44 from Jonathan Wakely ---
Or my view on what our tests should do have "evolved" (i.e. completely
contradicted my old view!)
If mingw says that isn't a valid program or simply can't support it for valid
reasons, then the right
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64883
--- Comment #43 from nightstrike ---
Jon,
I was referring to your Comment 9:
The failing test is only intended to check that libstdc++ is consistent about
using the uglified attributes. Anything outside libstdc++ can do whatever it
wants.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64883
--- Comment #42 from Jonathan Wakely ---
(In reply to nightstrike from comment #41)
> It seems to me that the test itself is a bit overzealous. If the intent is
> to ensure just that libstdc++ sources don't use certain words, well that's
> not
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64883
nightstrike changed:
What|Removed |Added
CC||jon_y at users dot
sourceforge.net
On Wed, 15 Mar 2017, Andrew Jenner wrote:
> > I am assuming SPE and VLE do not support AltiVec or 64-bit PowerPC,
> > please correct me if that is incorrect. Also, is "normal" floating
> > point supported at all?
>
> My understanding is that SPE is only present in the e500v1, e500v2 and
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80257
--- Comment #2 from Dominique d'Humieres ---
What is the output of
subroutine ppTest(f)
implicit none
external f
call f()
end subroutine ppTest
Program RunTimeCheck
implicit none
external :: ppTest
procedure(), pointer :: pptr
On 03/29/2017 01:31 PM, Jakub Jelinek wrote:
Hi!
GCC 4.8 and earlier didn't allow in C++ initialization of VLA and
C doesn't allow it in any GCC release. This has changed when the
support for C++1y VLA has been added, then reverted, but apparently
only partially.
The question is, do we want
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80263
--- Comment #7 from Pedro Alves ---
I filed a corresponding GDB bug here:
Support DW_TAG_base_type with no name
https://sourceware.org/bugzilla/show_bug.cgi?id=21335
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80265
Jakub Jelinek changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80263
--- Comment #6 from Pedro Alves ---
Yes, agreed.
I haven't investigated yet why it ends up with that "",
but it's likely that the hack was incomplete and that's a red herring.
Hopefully GDB won't have some hard-to-eliminate dependency on a
ux/ilp32/libada"
"-mabi=ilp32" -fno-diagnostics-show-caret -gnatez -mlittle-endian
../../gcc/gcc/testsuite/gnat.dg/lto21_pkg2.adb
+===GNAT BUG DETECTED==+
| 7.0.1 20170330 (experimental) (aarch64-suse-linux) GCC error:|
|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80266
Andreas Schwab changed:
What|Removed |Added
Target Milestone|--- |7.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80265
Bug ID: 80265
Summary: __builtin_{memcmp,memchr,strlen} are not usable in
constexpr functions
Product: gcc
Version: 7.0.1
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80263
--- Comment #5 from Jakub Jelinek ---
For GDB, guess you should not warn for DWARF >= 5.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=33661
Andrew Pinski changed:
What|Removed |Added
CC||gdelugre.gcc at subvert dot
techno
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64951
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64951
Andrew Pinski changed:
What|Removed |Added
CC||blubban at gmail dot com
--- Comment #2
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80264
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
one: Compiler silently emits a blank function (other than an unused
variable warning)
Second: movl $42, %ebx (%eax on -O1 or higher)
Third: As expected
Tested versions:
g++ 7.0.1 20170330 x86_64-linux-gnu (Godbolt)
g++ 6.2.0-5ubuntu12 x86_64-linux-gnu (Lubuntu 16.10)
g++ 4.4.7-1ubuntu2 x86_64-linux-
On 3/29/17 6:29 PM, Peter Bergner wrote:
> On 3/29/17 5:28 PM, Segher Boessenkool wrote:
>>> +/* { dg-skip-if "" { powerpc*-*-darwin* } { "*" } { "" } } */
>>> +/* { dg-skip-if "" { powerpc*-*-*spe* } { "*" } { "" } } */
>>> +/* { dg-require-effective-target dfp } */
>>
>> You can leave off the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80263
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
--- Comment #4
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60818
--- Comment #18 from Segher Boessenkool ---
Okay, this I can reproduce (no -fPIC needed, not even -m32). Thanks!
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79876
--- Comment #13 from Jakub Jelinek ---
Seems libgomp has a bug that without {,G}OMP_STACKSIZE and with OMP_DISPLAY_ENV
it displays random (uninitialized) value for the stack size, so I need to test
something like:
2017-03-30 Jakub Jelinek
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79876
--- Comment #12 from Jakub Jelinek ---
Of course, the testcase was not using libgomp at all and OMP_STACKSIZE is an
env var used by libgomp only.
So, this means whatever darwin libpthread are using is using extremely small
default for the
Hello,
I am not sure if I can help you but...
On Thu, Mar 30, 2017 at 08:05:07AM +0200, Andre Groenewald wrote:
> I am discovering the awesome world of GCC internals. I managed to
> develop a basic front end. It can call internal and external functions
> and link with standard libraries. All is
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80263
--- Comment #3 from Pedro Alves ---
Possible solutions could be:
#1 - emit the underlying type instead.
#2 - emit no name.
#2 seems to be valid DWARF5, which says (page 103):
"A base type entry may have a DW_AT_name attribute whose value is
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77333
--- Comment #23 from Martin Jambor ---
Fixed on trunk so far. I will prepare & test backports.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80263
Richard Biener changed:
What|Removed |Added
Keywords||wrong-debug
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77333
--- Comment #22 from Martin Jambor ---
Author: jamborm
Date: Thu Mar 30 13:51:02 2017
New Revision: 246589
URL: https://gcc.gnu.org/viewcvs?rev=246589=gcc=rev
Log:
[PR 77333] Fixup fntypes of gimple calls of clones
2017-03-30 Martin Jambor
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80263
--- Comment #1 from Pedro Alves ---
The consequence is that that internal type's name can mask out a user-defined
type with the same name. For example:
$ cat sizetype2.c
char array[1];
typedef struct sizetype { char c; } sizetype;
sizetype sz;
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80263
Bug ID: 80263
Summary: gcc's internal type "sizetype" leaks out as base type
name in the DWARF info
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80206
Jakub Jelinek changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
On Thu, Mar 30, 2017 at 3:20 PM, Bin.Cheng wrote:
> On Thu, Mar 30, 2017 at 2:18 PM, Bin.Cheng wrote:
>> On Thu, Mar 30, 2017 at 1:44 PM, Richard Biener
>> wrote:
>>> On Thu, Mar 30, 2017 at 2:03 PM, Bin.Cheng
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79876
--- Comment #11 from Dominique d'Humieres ---
> and see what it prints?
RLIMIT_STACK cur 67104768 max 67104768
PTHREAD_STACK_MIN 8192
main thread pthread_get_stacksize_np 67104768
other thread pthread_get_stacksize_np 524288
other thread
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80206
--- Comment #5 from Jakub Jelinek ---
Author: jakub
Date: Thu Mar 30 13:29:28 2017
New Revision: 246588
URL: https://gcc.gnu.org/viewcvs?rev=246588=gcc=rev
Log:
PR target/80206
* config/i386/sse.md
(_vextract_mask): Use
On Thu, Mar 30, 2017 at 2:18 PM, Bin.Cheng wrote:
> On Thu, Mar 30, 2017 at 1:44 PM, Richard Biener
> wrote:
>> On Thu, Mar 30, 2017 at 2:03 PM, Bin.Cheng wrote:
>>> On Thu, Mar 30, 2017 at 11:37 AM, Richard Biener
>>>
On Thu, Mar 30, 2017 at 1:44 PM, Richard Biener
wrote:
> On Thu, Mar 30, 2017 at 2:03 PM, Bin.Cheng wrote:
>> On Thu, Mar 30, 2017 at 11:37 AM, Richard Biener
>> wrote:
>>> On Wed, Mar 29, 2017 at 5:22 PM, Bin.Cheng
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80173
Jakub Jelinek changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned
Hi Jakub,
On 30 Mar 00:36, Jakub Jelinek wrote:
> Hi!
>
> As the testcase shows, we ICE with -mavx512f -ffloat-store, because
> at -O0 during expansion the destination is MEM, and the corresponding dup
> operand is some pseudo. There are *_mask patterns that have just
> register_operand / =v for
On Thu, Mar 30, 2017 at 4:11 AM, Michael Haubenwallner
wrote:
> On 03/29/2017 10:21 PM, David Edelsohn wrote:
>> On Wed, Mar 29, 2017 at 3:50 PM, Jeff Law wrote:
>>> On 03/27/2017 09:41 AM, David Edelsohn wrote:
>
> As far as I
On Thu, Mar 30, 2017 at 2:03 PM, Bin.Cheng wrote:
> On Thu, Mar 30, 2017 at 11:37 AM, Richard Biener
> wrote:
>> On Wed, Mar 29, 2017 at 5:22 PM, Bin.Cheng wrote:
>>> On Tue, Mar 28, 2017 at 1:34 PM, Richard Biener
>>>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80233
--- Comment #8 from Jakub Jelinek ---
It is probably latent there, there were major changes in the trap and
conditional trap handling in GCC 7, so we likely don't have a testcase right
now that would ICE in 6.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80233
--- Comment #7 from Segher Boessenkool ---
Is it fixed? Can this not happen on GCC 6?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80232
--- Comment #5 from vincenzo Innocente ---
I confirm that gather is almost twice as fast on
Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz
w/r/t
Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz
(used a benchmark version of PR80248 example)
so on skylake,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80262
--- Comment #5 from rguenther at suse dot de ---
On Thu, 30 Mar 2017, stefan at reservoir dot com wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80262
>
> --- Comment #4 from Stefan M Freudenberger ---
> My original example involved a
On Thu, Mar 30, 2017 at 11:37 AM, Richard Biener
wrote:
> On Wed, Mar 29, 2017 at 5:22 PM, Bin.Cheng wrote:
>> On Tue, Mar 28, 2017 at 1:34 PM, Richard Biener
>> wrote:
>>> On Tue, Mar 28, 2017 at 2:01 PM, Bin Cheng
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80262
--- Comment #4 from Stefan M Freudenberger ---
My original example involved a MEM with a constant offset, and yielded an ICE:
internal compiler error: tree check: expected integer_cst, have
addr_space_convert_expr in decompose, at tree.h
Maybe
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80251
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
--- Comment #3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80173
Marek Polacek changed:
What|Removed |Added
CC||mpolacek at gcc dot gnu.org
--- Comment
On Wed, 29 Mar 2017, Martin Jambor wrote:
> Hi,
>
> On Thu, Mar 16, 2017 at 05:57:51PM +0100, Martin Jambor wrote:
> > Hi,
> >
> > On Mon, Mar 13, 2017 at 01:46:47PM +0100, Richard Biener wrote:
> > > On Fri, 10 Mar 2017, Martin Jambor wrote:
> > >
> > > > Hi,
> > > >
> > > > PR 77333 is a
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80135
Marek Polacek changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=35878
Ville Voutilainen changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |ville.voutilainen at
gmail
1 - 100 of 136 matches
Mail list logo