On Wed, Sep 7, 2016 at 1:52 PM, Thomas Schwinge wrote:
> Hi!
>
> I trimmed the CC list -- I'm looking for advice about debugging a lto1
> ICE.
>
> On Fri, 19 Aug 2016 11:05:59 +, Joseph Myers
> wrote:
>> On Fri, 19 Aug 2016, Richard Biener
Hi!
I trimmed the CC list -- I'm looking for advice about debugging a lto1
ICE.
On Fri, 19 Aug 2016 11:05:59 +, Joseph Myers
wrote:
> On Fri, 19 Aug 2016, Richard Biener wrote:
> > Can you quickly verify if LTO works with the new types? I don't see
> > anything
>
On Tue, Sep 6, 2016 at 11:55 PM, Thomas Schwinge
wrote:
> Hi!
>
> Neither do I really know anything about Xtensa, nor do I have a lot of
> experience in these parts of GCC back ends, but:
There is a lot of background to know here. Unfortunately, I have no
familiarity
On 09/01/2016 09:04 AM, Martin Sebor wrote:
Understood. I think a write-only attribute or type qualifier would
make sense. Until/unless it's implemented I would recommend to work
around its absence by hiding access to the registers behind a read-
only and write-only functional API.
As you
On Wed, Sep 7, 2016 at 9:21 AM, augustine.sterl...@gmail.com
wrote:
> Hope this helps, and I'm happy to answer more questions.
Also, one technique commonly used by people who ship software for
Xtensa is to write it such that it could compile for any variant at
all.
Hi!
Neither do I really know anything about Xtensa, nor do I have a lot of
experience in these parts of GCC back ends, but:
On Tue, 6 Sep 2016 20:42:53 +0200, Oleksij Rempel
wrote:
> i'm one of ath9k-htc-firmware developers. Currently i'm looking for the
> way to
Hello,
On Tue, Sep 6, 2016 at 11:42 AM, Oleksij Rempel wrote:
> i'm one of ath9k-htc-firmware developers. Currently i'm looking for the
> way to provide this firmware as opensource/free package for debian. Main
> problem seems to be the need to patch gcc xtensa-config.h
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77509
Martin Liška changed:
What|Removed |Added
Keywords||ice-on-invalid-code
On Mon, Sep 5, 2016 at 6:11 PM, Tom de Vries wrote:
> On 05/09/16 09:49, Richard Biener wrote:
>>
>> On Sun, Sep 4, 2016 at 11:30 PM, Tom de Vries
>> wrote:
>>>
>>> > On 04/09/16 16:08, Richard Biener wrote:
>>
>> On September 4,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77359
--- Comment #14 from Dominik Vogt ---
Okay, it looks like outgoing_args_size is rounded up to a multiple of
preferred_stack_boundary, so there's no problem on s390 or other targets with a
stack allocation size smaller than STACK_BOUNDARY. So,
On 09/06/2016 12:51 PM, Bin Cheng wrote:
Hi,
This patch checks if loop has enough niters for peeling for data access gaps in
vect_analyze_loop_2, while now this check is in vect_transform_loop stage. The
problem is vectorizer may vectorize loops without enough iterations and
generate false
On Wed, Sep 7, 2016 at 1:52 PM, Thomas Schwinge wrote:
> Hi!
>
> I trimmed the CC list -- I'm looking for advice about debugging a lto1
> ICE.
>
> On Fri, 19 Aug 2016 11:05:59 +, Joseph Myers
> wrote:
>> On Fri, 19 Aug 2016, Richard Biener
Hi all,
The duplicate mode check in synth can just be deleted IMO. It was introduced as
part of r139821 that was
a much larger change introducing size/speed differentiation to the RTL midend.
So I think it's just a typo/copy-pasto.
Tested on aarch64-none-elf.
Ok?
Thanks,
Kyrill
2016-09-07
On 09/06/2016 12:49 PM, Bin Cheng wrote:
Hi,
This is a patch set generating new control flow graph for vectorized loop and
its peeling loops. At the moment, CFG for vecorized loop is complicated and
sub-optimal. Major issues are like:
A) For both prologue and vectorized loop, it generates
On 09/06/2016 12:52 PM, Bin Cheng wrote:
Hi,
This simple patch changes slpeel_tree_duplicate_loop_edge_cfg by putting copied
loop after its new preheader and after the original loop's latch in basic
block's linked list. It doesn't change CFG at all, but makes the dump cfg a
little bit easier
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77393
--- Comment #14 from ro at CeBiTec dot Uni-Bielefeld.DE ---
> --- Comment #13 from Jerry DeLisle ---
> Author: jvdelisle
> Date: Tue Sep 6 23:22:26 2016
> New Revision: 240018
>
> URL: https://gcc.gnu.org/viewcvs?rev=240018=gcc=rev
> Log:
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77513
--- Comment #1 from Andreas Schwab ---
The "3" flag on the line marker marks the following lines as originating from a
system header where warnings are suppressed. Use -Wsystem-headers to enable
them.
On Wed, Sep 07, 2016 at 11:15:34AM +0200, Florian Weimer wrote:
> On 09/06/2016 11:31 PM, Paul Eggert wrote:
> >On 09/06/2016 01:40 PM, Joseph Myers wrote:
> >>Sounds like a defect in C11 to me - none of the examples of flexible
> >>array
> >>members anticipate needing to add to the size to allow
On 09/06/2016 12:50 PM, Bin Cheng wrote:
Hi,
This simple patch adds interface reseting original copy table in cfg.c. This
will be used in rewriting vect_do_peeling_* functions in vectorizer so that we
don't need to release/allocate tables between prolog and epilog peeling.
Thanks,
bin
On 09/06/2016 12:53 PM, Bin Cheng wrote:
Hi,
After CFG changes in vectorizer, the epilog loop now can be completely peeled,
resulting in changes in the number of instructions that these tests check.
This patch adjusts related checking strings.
Thanks,
bin
gcc/testsuite/ChangeLog
2016-09-01
On 09/07/2016 02:19 AM, Richard Biener wrote:
On Tue, 6 Sep 2016, Jakub Jelinek wrote:
On Tue, Sep 06, 2016 at 04:59:23PM +0100, Kyrill Tkachov wrote:
On 06/09/16 16:32, Jakub Jelinek wrote:
On Tue, Sep 06, 2016 at 04:14:47PM +0100, Kyrill Tkachov wrote:
The v3 of this patch addresses
Hi Fritz,
please note: I do not have official review privileges. So my vote here
is rather an advise to you and the official reviewers. Often such a
inofficial review helps to speed things up, because the official ones
are pointed to the nics and nacs and don't have to bother with the
minor
On 09/07/2016 10:19 AM, Richard Biener wrote:
On Tue, 6 Sep 2016, Jakub Jelinek wrote:
If you want a 64-bit store, you'd need to merge the two, and that would be
even more expensive. It is a matter of say:
movl $0x12345678, (%rsp)
movl $0x09abcdef, 4(%rsp)
vs.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=57117
--- Comment #13 from vehre at gcc dot gnu.org ---
Created attachment 39581
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=39581=edit
Shorter version to fix the issue.
Hi all,
Dominique pointed out, that the patches proposed by Paul
Hi!
I trimmed the CC list -- I'm looking for advice about debugging a lto1
ICE.
On Fri, 19 Aug 2016 11:05:59 +, Joseph Myers
wrote:
> On Fri, 19 Aug 2016, Richard Biener wrote:
> > Can you quickly verify if LTO works with the new types? I don't see
> > anything
>
On 09/06/2016 12:51 PM, Bin Cheng wrote:
Hi,
Current implementation requires that variables live outside of vect-loop
satisfying LCSSA form, this patch relaxes the restriction. It keeps the old
behavior for LCSSA PHI node by replacing use of live var with result of that
PHI; for other uses
On 09/06/2016 12:53 PM, Bin Cheng wrote:
Hi,
For loops which are bounded to iterate only 1 time (thus loop's latch doesn't
roll), there is nothing to predictive common, this patch detects/skips these
cases. A test is also added in
gcc/testsuite/gfortran.dg/vect/fast-math-mgrid-resid.f for
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77513
--- Comment #2 from petschy at gmail dot com ---
I don't want to enable them. The problem is not with too little but too many
warnings.
A snippet from one of the problematic files:
{ NULL, NULL, false, false }
is preprocessed to
{
On 06/09/16 14:14, Wilco Dijkstra wrote:
> Improve aarch64_legitimize_address - avoid splitting the offset if it is
> supported. When we do split, take the mode size into account. BLKmode
> falls into the unaligned case but should be treated like LDP/STP.
> This improves codesize slightly due to
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77377
Martin Liška changed:
What|Removed |Added
CC||zsojka at seznam dot cz
--- Comment #6
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77401
Martin Liška changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77498
Richard Biener changed:
What|Removed |Added
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77497
Richard Biener changed:
What|Removed |Added
Target Milestone|--- |5.5
Summary|Setting DWARF
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77483
--- Comment #4 from ro at CeBiTec dot Uni-Bielefeld.DE ---
> --- Comment #3 from Richard Biener ---
> You could add dg-skip-if or XFAILs to the tests now failing. IMHO a testsuite
> issue.
I though about just adding -mno-stackrealign to the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=1
Florian Weimer changed:
What|Removed |Added
Status|RESOLVED|UNCONFIRMED
Resolution|INVALID
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77512
Bug ID: 77512
Summary: gcc compilation stops with Arithmetic Exception
Product: gcc
Version: 6.2.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component:
On Wed, Sep 7, 2016 at 1:10 AM, kugan wrote:
> Hi Bin,
>
>
> On 07/09/16 04:54, Bin Cheng wrote:
>>
>> Hi,
>> LOOP_VINFO_NITERS is computed as LOOP_VINFO_NITERSM1 + 1, which could
>> overflow in loop niters' type. Vectorizer needs to generate more code
>>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=29842
Bug 29842 depends on bug 24194, which changed state.
Bug 24194 Summary: emit_input_reload_insns secondary reload handling is unsafe
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=24194
What|Removed |Added
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77304
Martin Liška changed:
What|Removed |Added
Last reconfirmed||2016-9-7
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=24194
Andrew Pinski changed:
What|Removed |Added
Status|WAITING |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=30199
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77450
--- Comment #6 from Richard Biener ---
Author: rguenth
Date: Wed Sep 7 08:22:01 2016
New Revision: 240025
URL: https://gcc.gnu.org/viewcvs?rev=240025=gcc=rev
Log:
2016-09-07 Richard Biener
PR c/77450
*
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=31566
Andrew Pinski changed:
What|Removed |Added
Keywords||easyhack
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77510
Bug ID: 77510
Summary: genautomata memory footprint for MIPS
Product: gcc
Version: 5.4.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: bootstrap
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77493
--- Comment #13 from Jonathan Wakely ---
(In reply to Richard Biener from comment #11)
> CCing libstdc++ people -- not sure if std::stable_sort (on which kind of
> collection?) is safe for std::shared_ptr.
It's required to work correctly. It
On 09/06/2016 11:31 PM, Paul Eggert wrote:
On 09/06/2016 01:40 PM, Joseph Myers wrote:
Sounds like a defect in C11 to me - none of the examples of flexible
array
members anticipate needing to add to the size to allow for tail padding
with unknown alignment requirements.
Yes, I would prefer
d=c++14
-Wzero-as-null-pointer-constant 20160907-null.cpp -E > 20160907-null.ii
Yesterday I switched on the warning for a ~250kloc codebase to clean it up.
Used 7.0, it was tedious but it was done. I had to replace NULLs also, not just
0s, but at that time I wasn't suspecting anything, though it
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77499
--- Comment #5 from Andrew Pinski ---
(In reply to Richard Biener from comment #3)
> It seems with thumb the code is only if-converted after reload for some
> reason.
Most likely because it is going through the cond_exec route.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77347
Martin Liška changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=10802
Andrew Pinski changed:
What|Removed |Added
Status|NEW |WAITING
--- Comment #14 from Andrew
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77508
Martin Liška changed:
What|Removed |Added
Keywords||ice-on-valid-code
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=21786
Andrew Pinski changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77503
--- Comment #11 from Markus Trippelsdorf ---
(In reply to Andrew Pinski from comment #10)
> (In reply to Markus Trippelsdorf from comment #6)
> > markus@x4 tmp % cat fsmpage.i
>
> You got to it before I could do that :).
Yeah, sorry. I already
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77499
--- Comment #7 from avieira at gcc dot gnu.org ---
if-convert is a no go here, for the reason Andrew pointed out, sorry missed
that comment!
So I dont know... Only thing I can think of is better "value-range"-like
analysis for combine, but that
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77503
--- Comment #12 from amker at gcc dot gnu.org ---
ICE is because prologue peeling changes code (to be specific, the initial
argument of reduction phi node in loop header), as a result, the statement to
be vectorized is not the statement that was
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77499
--- Comment #9 from avieira at gcc dot gnu.org ---
> > So I dont know... Only thing I can think of is better "value-range"-like
> > analysis for combine, but that might be too costly?
>
> So we are not really looking for combine to combine the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77503
--- Comment #13 from amker at gcc dot gnu.org ---
(In reply to amker from comment #12)
> ICE is because prologue peeling changes code (to be specific, the initial
> argument of reduction phi node in loop header), as a result, the statement
> to
On 08/18/2016 06:06 PM, Richard Biener wrote:
> On August 18, 2016 5:54:49 PM GMT+02:00, Jakub Jelinek
> wrote:
>> On Thu, Aug 18, 2016 at 08:51:31AM -0700, Andi Kleen wrote:
I'd prefer to make updates atomic in multi-threaded applications.
The best proxy we have for
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77383
Martin Liška changed:
What|Removed |Added
Keywords||ice-on-valid-code
On Wed, 7 Sep 2016, Yvan Roux wrote:
> Hi Richard,
>
> On 6 September 2016 at 14:41, Richard Biener wrote:
> >
> > The following fixes PR77450.
> >
> > Bootstrapped and tested on x86_64-unknown-linux-gnu, applied to trunk.
> >
> > Richard.
> >
> > 2016-09-06 Richard Biener
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=30136
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |WAITING
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77501
Richard Biener changed:
What|Removed |Added
Keywords||ice-on-invalid-code
Target
On Tue, Sep 6, 2016 at 10:43 AM, Pierre-Marie de Rodat
wrote:
> Hello,
>
> On 08/29/2016 11:03 AM, Pierre-Marie de Rodat wrote:
>>
>> Here is another attempt to solve the original issue. This time, with a
>> proper testcase. ;-)
>>
>> Rebased against trunk, boostrapped and
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77508
Bug ID: 77508
Summary: ICE on valid C++ code: in
finish_class_member_access_expr, at cp/typeck.c:2783
Product: gcc
Version: 7.0
Status: UNCONFIRMED
Severity:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=16200
Andrew Pinski changed:
What|Removed |Added
Status|WAITING |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77499
--- Comment #6 from avieira at gcc dot gnu.org ---
> so we are talking about the uxthne insn (I don't know arm / thumb very well).
Yes, the uxthne is the "zero_extend" that is otherwise optimized away if you
turn off code-hoisting.
This is
On 09/07/2016 09:45 AM, Christophe Lyon wrote:
> On 6 September 2016 at 15:45, Martin Liška wrote:
>> On 09/06/2016 03:31 PM, Jakub Jelinek wrote:
>>> sizeof (gcov_type) talks about the host gcov type, you want instead the
>>> target gcov type. So
>>> TYPE_SIZE (gcov_type_node)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77511
Bug ID: 77511
Summary: libbacktrace could not find executable to open
Product: gcc
Version: 6.2.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
On 06/09/16 22:17, Jeff Law wrote:
> On 09/06/2016 03:08 AM, Jakub Jelinek wrote:
>> On Tue, Sep 06, 2016 at 11:06:36AM +0200, Richard Biener wrote:
>>> On Mon, Sep 5, 2016 at 6:17 PM, Andrew Haley wrote:
On 05/09/16 17:15, Richard Biener wrote:
> On September 5, 2016
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77499
--- Comment #4 from Richard Biener ---
Oh, and with -fno-code-hoisting I see
movwr6, #45345
.L5:
smull lr, r4, r5, r1
sub r4, r4, r1, asr #31
add r4, r4, r4, lsl #1
cmp r1, r4
I am not sure about the process, but it may also be nice/useful to add your new
macro to ForEachMacros in contrib/clang-format.
Dominik
> On 07 Sep 2016, at 02:21, Kugan Vivekanandarajah
> wrote:
>
> Hi Richard,
>
> On 6 September 2016 at 19:08, Richard
On Tue, 6 Sep 2016, Jakub Jelinek wrote:
> On Tue, Sep 06, 2016 at 04:59:23PM +0100, Kyrill Tkachov wrote:
> > On 06/09/16 16:32, Jakub Jelinek wrote:
> > >On Tue, Sep 06, 2016 at 04:14:47PM +0100, Kyrill Tkachov wrote:
> > >>The v3 of this patch addresses feedback I received on the version
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=20192
Andrew Pinski changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
On 09/06/2016 10:40 PM, Joseph Myers wrote:
On Tue, 6 Sep 2016, Paul Eggert wrote:
One way to correct the code is to increase malloc's argument up to a multiple
of alignof(max_align_t). (One cannot portably use alignof(struct s) due to
Sounds like a defect in C11 to me - none of the examples
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77499
--- Comment #8 from rguenther at suse dot de ---
On Wed, 7 Sep 2016, avieira at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77499
>
> --- Comment #7 from avieira at gcc dot gnu.org ---
> if-convert is a no go here,
Various places in GCC use negate, bit-and and compare to test whether
an integer is a power of 2, but I think it would be clearer for this
test to be wrapped in a function.
OK for trunk?
commit e2ca9914ce46d56775854f50c21506b220fd50b6
Author: Jason Merrill
Date: Wed Sep 7
On Wed, Aug 31, 2016 at 12:29 PM, Uros Bizjak wrote:
>> the new STV pass generates SSE instructions in 32-bit mode very late in the
>> pipeline and doesn't bother about realigning the stack, so it wreaks havoc on
>> OSes where you need to realign the stack, e.g. Windows, but I
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77483
H.J. Lu changed:
What|Removed |Added
CC||hjl.tools at gmail dot com
--- Comment #5
Ping this patch:
https://gcc.gnu.org/ml/gcc-patches/2016-08/msg02099.html
Peter
On Tue, Sep 6, 2016 at 8:06 PM, Eric Gallager wrote:
> On 9/6/16, Uros Bizjak wrote:
>> On Tue, Sep 6, 2016 at 5:33 PM, Eric Gallager wrote:
>>> Ping? CC-ing an i386 maintainer since the patch mostly touches
>>> i386-specific files.
On 7 September 2016 at 11:34, Martin Liška wrote:
> On 09/07/2016 09:45 AM, Christophe Lyon wrote:
>> On 6 September 2016 at 15:45, Martin Liška wrote:
>>> On 09/06/2016 03:31 PM, Jakub Jelinek wrote:
sizeof (gcov_type) talks about the host gcov type, you
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63346
--- Comment #5 from Peter Seiderer ---
Seems to be fixed in 5.4.0, tested with the original buildroot/xserver/dillo
testcase (with up to date buildroot) and the provided fbpict.c testcase.
Hi,
This patch arranges for half-precision complex multiply and divide
routines to be built if __LIBGCC_HAS_HF_MODE__. This will be true
if the target supports the _Float16 type.
OK?
Thanks,
James
---
libgcc/
2016-09-07 James Greenhalgh
* Makefile.in
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77513
--- Comment #3 from Jonathan Wakely ---
(In reply to petschy from comment #0)
> For c++11 and later code, why is NULL defined as __null, rather than nullptr?
Because defining NULL as nullptr would violate the requirements of the
standard, which
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60483
vehre at gcc dot gnu.org changed:
What|Removed |Added
Status|NEW |ASSIGNED
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66459
Manuel López-Ibáñez changed:
What|Removed |Added
CC||manu at gcc dot gnu.org
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71710
--- Comment #3 from Zhendong Su ---
A related, but simpler test that triggers the same ICE:
template < typename > struct A
{
A a;
template < int > using B = decltype (a);
B < 0 > b;
};
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77475
--- Comment #4 from Christophe Lyon ---
Author: clyon
Date: Wed Sep 7 20:18:17 2016
New Revision: 240030
URL: https://gcc.gnu.org/viewcvs?rev=240030=gcc=rev
Log:
PR middle-end/77475: Fix AArch64 testcases.
2016-09-07 Jakub Jelinek
On September 6, 2016 5:14:47 PM GMT+02:00, Kyrill Tkachov
wrote:
>Hi all,
s/contigous/contiguous/
s/ where where/ where/
+struct merged_store_group
+{
+ HOST_WIDE_INT start;
+ HOST_WIDE_INT width;
+ unsigned char *val;
+ unsigned int align;
+ auto_vec stores;
On Wed, Sep 07, 2016 at 10:19:11AM +0200, Richard Biener wrote:
> > If you want a 64-bit store, you'd need to merge the two, and that would be
> > even more expensive. It is a matter of say:
> > movl $0x12345678, (%rsp)
> > movl $0x09abcdef, 4(%rsp)
> > vs.
> > movabsq
On 09/07/16 22:04, Joseph Myers wrote:
> On Wed, 7 Sep 2016, Bernd Edlinger wrote:
>
>> interesting. I just tried the test case from PR 77330 with _Decimal128.
>> result: _Decimal128 did *not* trap with gcc4.8.4, but it does trap with
>> gcc-7.0.0.
>
> I checked with GCC 4.3; __alignof__
Dear all,
the attached patch supports failed images also when -fcoarray=single is used.
Built and regtested on x86_64-pc-linux-gnu.
Cheers,
Alessandro
2016-08-09 5:22 GMT-06:00 Paul Richard Thomas :
> Hi Sandro,
>
> As far as I can see, this is OK barring a couple
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=48298
--- Comment #19 from Paul Thomas ---
Author: pault
Date: Wed Sep 7 21:21:16 2016
New Revision: 240032
URL: https://gcc.gnu.org/viewcvs?rev=240032=gcc=rev
Log:
2016-09-07 Dominique Dhumieres
PR fortran/48298
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77521
Bug ID: 77521
Summary: %qc format directive should quote non-printable
characters
Product: gcc
Version: 7.0
Status: UNCONFIRMED
Severity: normal
On Wed, Sep 7, 2016 at 9:31 AM, Andre Vehreschild wrote:
> Hi Fritz,
>
> please note: I do not have official review privileges. So my vote here
> is rather an advise to you and the official reviewers. Often such a
> inofficial review helps to speed things up, because the official
On Wed, Sep 07, 2016 at 09:07:45AM +0200, Richard Biener wrote:
> > @@ -493,6 +504,8 @@ instrument_builtin_call (gimple_stmt_ite
> > if (!tree_fits_uhwi_p (last_arg)
> > || memmodel_base (tree_to_uhwi (last_arg)) >= MEMMODEL_LAST)
> > return;
> > + if
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77519
Bug ID: 77519
Summary: [5/6/7 Regression] complex multiply / divide excess
precision handling inverted
Product: gcc
Version: 7.0
Status: UNCONFIRMED
Severity:
On Wed, 7 Sep 2016, Joseph Myers wrote:
> How about instead having more than one target macro / hook. One would
> indicate that excess precision is used by insn patterns (and be set only
> for i386 and m68k). Another would indicate the API-level excess precision
Or, maybe there would be a
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77520
Martin Sebor changed:
What|Removed |Added
Keywords||diagnostic
Severity|normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77520
Bug ID: 77520
Summary: wrong value for extended ASCII characters in -Wformat
message
Product: gcc
Version: 7.0
Status: UNCONFIRMED
Severity: normal
1 - 100 of 174 matches
Mail list logo