https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78583
Segher Boessenkool changed:
What|Removed |Added
Status|NEW |ASSIGNED
> the patch at https://gcc.gnu.org/ml/fortran/2016-11/msg00246.html
> (the one going to gcc-patches was rejected due to size of
> regernerated files) contains one libgcc change, which exposes
> the __cpu_model interface fox i386 to libgfortran.
>
> The Fortran bits are OKd, but I need an approval
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78588
Markus Trippelsdorf changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78593
janus at gcc dot gnu.org changed:
What|Removed |Added
Keywords||ice-on-invalid-code
On 2016.11.29 at 15:25 -0600, Segher Boessenkool wrote:
> On Tue, Nov 29, 2016 at 05:00:05PM +0100, Markus Trippelsdorf wrote:
> > Building gcc with -fsanitize=undefined shows:
> > rtlanal.c:5210:38: runtime error: shift exponent 4294967295 is too large
> > for 64-bit type 'long unsigned int'
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78592
janus at gcc dot gnu.org changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Known to work|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78588
--- Comment #1 from Markus Trippelsdorf ---
Author: trippels
Date: Wed Nov 30 07:30:55 2016
New Revision: 242997
URL: https://gcc.gnu.org/viewcvs?rev=242997=gcc=rev
Log:
Fix PR78588 - rtlanal.c:5210:38: runtime error: shift exponent 4294967295
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78573
janus at gcc dot gnu.org changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
2016-11-29 23:21 GMT+01:00 Steve Kargl :
> On Tue, Nov 29, 2016 at 10:58:35PM +0100, Janus Weil wrote:
>>
>> here is a rather straightforward patch for an ice-on-invalid
>> regression. Regtests cleanly on x86_64-linux-gnu. Ok for trunk?
>>
>
> Yes.
Thanks,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78573
--- Comment #3 from janus at gcc dot gnu.org ---
Author: janus
Date: Wed Nov 30 07:25:36 2016
New Revision: 242996
URL: https://gcc.gnu.org/viewcvs?rev=242996=gcc=rev
Log:
2016-11-30 Janus Weil
PR fortran/78573
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78607
Bug ID: 78607
Summary: [7 Regression] ICE: verify_flow_info failed (error:
missing barrier after block 2)
Product: gcc
Version: 7.0
Status: UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78342
--- Comment #6 from Arseny Solokha ---
(In reply to Segher Boessenkool from comment #5)
> Please file a separate bug.
I've filed PR78607.
Hello world,
the patch at https://gcc.gnu.org/ml/fortran/2016-11/msg00246.html
(the one going to gcc-patches was rejected due to size of
regernerated files) contains one libgcc change, which exposes
the __cpu_model interface fox i386 to libgfortran.
The Fortran bits are OKd, but I need an
On Tue, Nov 29, 2016 at 8:44 PM, Jakub Jelinek wrote:
> Hi!
>
> The following testcase ICEs because DECL_RTL/DECL_INCOMING_RTL are adjusted
> by the stv pass through the PUT_MODE modifications, which means that for
> var-tracking.c they contain a bogus mode.
>
> Fixed by
Dear Andre,
This all looks OK to me. The only comment that I have that you might
deal with before committing is that some of the Boolean expressions,
eg:
+ int caf_dereg_mode
+ = ((caf_mode & GFC_STRUCTURE_CAF_MODE_IN_COARRAY) != 0
+ || c->attr.codimension)
+ ?
On Tuesday 29 November 2016 10:06 PM, Denis Chertykov wrote:
2016-11-28 10:17 GMT+03:00 Pitchumani Sivanupandi
:
On Saturday 26 November 2016 12:11 AM, Denis Chertykov wrote:
I'm sorry for delay.
I have a problem with the patch:
(Stripping trailing CRs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78529
--- Comment #13 from Andrew Pinski ---
https://gcc.gnu.org/ml/gcc-testresults/2016-11/msg03338.html
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78584
DJ Delorie changed:
What|Removed |Added
Status|NEW |ASSIGNED
--- Comment #6 from DJ Delorie
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78584
--- Comment #5 from Florian Weimer ---
Hmm. Maybe it is file-system-specific. I don't see the anomalous return
values on XFS and tmpfs.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78529
Andrew Pinski changed:
What|Removed |Added
Target|aarch64 |aarch64-elf
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78584
--- Comment #4 from DJ Delorie ---
kernel-4.8.6-201.fc24.x86_64
glibc-2.23.1-11.fc24.x86_64
but I'm also working on a libiberty patch to detect the case and avoid it.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78584
Florian Weimer changed:
What|Removed |Added
CC||fw at gcc dot gnu.org
--- Comment #3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78529
--- Comment #11 from Jim Wilson ---
FYI I'm using the gdb simulator to run the testcases.
These two patches to fix PRs 78602 and 78560 fix aspects of the vector set and
extract code I've been working on in the last couple of months.
The two symptoms were essentially the same thing, one on vector set and the
other on vector extract. The core issue was both set and extract did not
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78599
--- Comment #2 from prathamesh3492 at gcc dot gnu.org ---
Hi Markus,
Thanks for the report, I am able to reproduce it with ubsan-built gcc
(--with-build-config=bootstrap-ubsan) on x86_64-unknown-linux-gnu.
I am looking into it.
Thanks,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55177
Andrew Pinski changed:
What|Removed |Added
Keywords||TREE
--- Comment #19 from Andrew Pinski
On Tue, Nov 29, 2016 at 1:09 AM, Kyrill Tkachov
wrote:
> Hi all,
>
> This ICE only occurs on big-endian ILP32 -fpie code. The expansion code
> generates the invalid load:
> (insn 6 5 7 (set (reg/f:SI 76)
> (unspec:SI [
> (mem/u/c:SI (lo_sum:SI
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=23681
Andrew Pinski changed:
What|Removed |Added
Status|ASSIGNED|NEW
Assignee|pinskia at gcc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=46888
Andrew Pinski changed:
What|Removed |Added
Status|ASSIGNED|NEW
Assignee|pinskia at gcc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=24775
Andrew Pinski changed:
What|Removed |Added
Assignee|pinskia at gcc dot gnu.org |unassigned at gcc dot
gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=36165
Andrew Pinski changed:
What|Removed |Added
Status|ASSIGNED|NEW
Assignee|pinskia at gcc
Now I've merged GCC trunk revision 242992 to the gccgo branch.
Ian
Please excuse the messy formatting in my initial mail. Resending with proper
formatting.
This patch checks for negative character length in the array constructor, and
treats it as LEN=0.
A warning message is also printed if bounds checking is enabled.
Bootstrapped and regression tested the
This patch checks for negative character length in the array constructor,
and treats it as LEN=0. A warning message is also printed if bounds checking is
enabled.
Bootstrapped and regression tested the patch on x86_64-linux-gnu and
aarch64-linux-gnu.
Index: ChangeLog
There's a couple unused variables in arc_handle_option. This patch
removes them. Verified the arc port builds again.
Installed on the trunk.
Jeff
commit 0177a97d002107d99f82be0861ac0052285ccc0a
Author: law
Date: Wed Nov 30 04:37:10 2016 +
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78549
--- Comment #8 from Jerry DeLisle ---
(In reply to Jerry DeLisle from comment #7)
Correction:
> Regardless, I will be looking at pr78351 (which is a result of doing some
> speedups for internal units) and I will be thinking more about this PR
On 11/02/2016 01:20 PM, Bernd Schmidt wrote:
On 10/29/2016 06:21 PM, Jeff Law wrote:
On a small number of ports, we only have 2 defined register classes.
NO_REGS and ALL_REGS. Examples would include nvptx and vax.
So let's look at check_and_process_move from lra-constraints.c:
sclass =
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78549
--- Comment #7 from Jerry DeLisle ---
(In reply to mecej4 from comment #6)
> (In reply to Jerry DeLisle from comment #5)
> >
> > Can you explain what "Windows Subsystem for Linux (Ubuntu 14) on Windows-10"
> > is?
>
> Sorry if I created a bad
On 11/19/2016 02:04 PM, Martin Sebor wrote:
On 10/26/2016 02:46 PM, Joseph Myers wrote:
On Wed, 26 Oct 2016, Martin Sebor wrote:
The attached patch implements one such approach by having the pretty
printer recognize the space format flag to suppress the type suffix,
so "%E" still prints the
On 11/29/2016 08:38 PM, Jerry DeLisle wrote:
I had to do this to get my build to work.
diff --git a/gcc/doc/install.texi b/gcc/doc/install.texi
index 5d96e5fd..140ff807 100644
--- a/gcc/doc/install.texi
+++ b/gcc/doc/install.texi
@@ -2196,7 +2196,7 @@ continues.
@itemx
On 11/26/2016 05:52 PM, Martin Sebor wrote:
On 11/25/2016 12:51 PM, Jeff Law wrote:
On 11/23/2016 06:15 PM, Martin Sebor wrote:
gcc_assert works only in some instances (e.g., in c-ada-spec.c:191)
but not in others because some actually do make the alloca(0) call
at runtime: at a minimum,
I had to do this to get my build to work.
diff --git a/gcc/doc/install.texi b/gcc/doc/install.texi
index 5d96e5fd..140ff807 100644
--- a/gcc/doc/install.texi
+++ b/gcc/doc/install.texi
@@ -2196,7 +2196,7 @@ continues.
@itemx --with-target-bdw-gc-lib=@var{list}
Specify search directories for
That said, I defer to you on how to proceed here. I'm prepared
to do the work(*) but I do worry about jeopardizing the chances
of this patch and the others making it into 7.0.
So would it make sense to just init/fini the b_o_s framework in your
pass and for builtin expansion?
I think that
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78549
--- Comment #6 from mecej4 at operamail dot com ---
(In reply to Jerry DeLisle from comment #5)
>
> Can you explain what "Windows Subsystem for Linux (Ubuntu 14) on Windows-10"
> is?
Sorry if I created a bad portmanteau phrase.
Here is a link
On 11/29/2016 03:44 AM, Martin Liška wrote:
Currently we an assert that prevents proper use-after-scope sanitization
in nested functions. With the attached patch, we are able to do so.
I'm adding 2 test-cases, first one is the ICE reported in PR and the second
one tests proper report of
Hi Jeff,
>> I believe Richi asked for a small change after which you can consider
>> the patch approved:
Yeah. Thanks for all the comments and reviews.
Patch committed after the modification as:-
https://gcc.gnu.org/ml/gcc-cvs/2016-11/msg01019.html
Thanks,
Naveen
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78606
Bug ID: 78606
Summary: -Wformat-length/-fprintf-return-value incorrect for
%+.0i and %.0o with zero value
Product: gcc
Version: 7.0
Status: UNCONFIRMED
This patch to libgo fixes a couple of problems that arise when
building Go code into an archive or shared library that is linked into
a C program.
In archive mode, initsig is called before the memory allocator has
been initialized. The code was doing a memory allocation because of
the call to
On 11/29/2016 12:48 PM, Jakub Jelinek wrote:
Hi!
As mentioned in the PR, the LSHIFT_EXPR computation of values that
will need longest or shortest string is both incorrect (it shifts
integer_one_node left, so for precisions above precision of integer
it returns 0 (not to mention that it is
On 11/18/2016 03:24 AM, Jakub Jelinek wrote:
> On Sat, Nov 12, 2016 at 08:51:00AM -0800, Cesar Philippidis wrote:
>> On 11/11/2016 02:34 AM, Jakub Jelinek wrote:
>>> On Thu, Nov 10, 2016 at 06:46:46PM +0800, Chung-Lin Tang wrote:
>>
>> And here's the patch.
>
> The patch doesn't look like OpenACC
On Tue, 2016-11-29 at 18:20 -0700, Sandra Loosemore wrote:
> On 11/29/2016 06:10 PM, David Malcolm wrote:
> > [snip]
> >
> > r242985 seems to have broken the build, for me at least (with
> > texinfo
> > 5.1):
> >
> > ../../src/gcc/doc/install.texi:2199: use braces to give a command
> > as an
On 11/29/2016 06:10 PM, David Malcolm wrote:
[snip]
r242985 seems to have broken the build, for me at least (with texinfo
5.1):
../../src/gcc/doc/install.texi:2199: use braces to give a command as an
argument to @=
make[2]: *** [doc/gccinstall.info] Error 1
The attached patch fixes it.
OK
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78569
David Malcolm changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
The ICE in PR preprocessor/78569 appears to be due to an attempt to
generate substring locations in a .i file where the underlying .c file
has changed since the .i file was generated.
This can't work, so it seems safest for the on-demand substring
locations to be unavailable for such files,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78569
--- Comment #5 from David Malcolm ---
Author: dmalcolm
Date: Wed Nov 30 01:13:37 2016
New Revision: 242990
URL: https://gcc.gnu.org/viewcvs?rev=242990=gcc=rev
Log:
substring locations and # line directives (PR preprocessor/78569)
The ICE in PR
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78576
Bill Schmidt changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
On Tue, 2016-11-29 at 14:23 -0700, Jeff Law wrote:
> On 11/21/2016 04:23 PM, Matthias Klose wrote:
> > On 21.11.2016 18:16, Rainer Orth wrote:
> > > Hi Matthias,
> > >
> > > > ahh, didn't see that :-/ Now fixed, is this clearer now?
> > > >
> > > > The options
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78605
--- Comment #1 from joseph at codesourcery dot com ---
On Tue, 29 Nov 2016, msebor at gcc dot gnu.org wrote:
> As an independent issue, since the type of the arguments to the %f directive
> is
> float (not double), the checker should use
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70905
Bernd Schmidt changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78576
--- Comment #14 from joseph at codesourcery dot com ---
On Tue, 29 Nov 2016, bergner at gcc dot gnu.org wrote:
> Using gdb, I see:
>
> (gdb) info registers f1 f2
> f1 27 (raw 0x403b)
> f2
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78597
--- Comment #1 from joseph at codesourcery dot com ---
If these fail but weren't previously run then it's not a regression, but
an indication of a wrong-code bug in the float128 support for powerpc (for
which testing was previously very
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78532
--- Comment #5 from joseph at codesourcery dot com ---
On Tue, 29 Nov 2016, m.ostapenko at samsung dot com wrote:
> /home/max/src/glibc/resolv/ns_print.c:99: undefined reference to
> `__stack_chk_guard'
You get this if glibc and GCC have
On 11/29/2016 12:48 PM, Jakub Jelinek wrote:
Hi!
As mentioned in the PR, the LSHIFT_EXPR computation of values that
will need longest or shortest string is both incorrect (it shifts
integer_one_node left, so for precisions above precision of integer
it returns 0 (not to mention that it is
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78594
--- Comment #4 from Michael Meissner ---
Fixed in subversion id 242983.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78594
Michael Meissner changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78594
--- Comment #2 from Michael Meissner ---
Author: meissner
Date: Wed Nov 30 00:05:46 2016
New Revision: 242983
URL: https://gcc.gnu.org/viewcvs?rev=242983=gcc=rev
Log:
2016-11-29 Michael Meissner
PR
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78532
--- Comment #4 from Matthias Klose ---
using the glibc build from Debian unstable, build logs at
https://buildd.debian.org/status/package.php?p=glibc
see https://buildd.debian.org/status/logs.php?pkg=glibc=sparc64
for the last successful build.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78586
--- Comment #6 from Martin Sebor ---
(In reply to Jakub Jelinek from comment #5)
> There are still various weird spots in format_integer.
> E.g.
> else if (TREE_CODE (TREE_TYPE (arg)) == INTEGER_TYPE
>|| TREE_CODE (TREE_TYPE (arg))
Hi Jerry,
Tests with multiple images go into the opencoarrays testsuite. Still to push
though. The tests I have so far all pass.
- Andre
Am 30. November 2016 00:06:22 MEZ, schrieb Jerry DeLisle
:
>On 11/28/2016 10:33 AM, Andre Vehreschild wrote:
>> PING!
>>
>> I know
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78560
Michael Meissner changed:
What|Removed |Added
Attachment #40194|0 |1
is obsolete|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78426
--- Comment #5 from Kazumoto Kojima ---
Fixed on 5/6 branches too.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78426
--- Comment #4 from Kazumoto Kojima ---
Author: kkojima
Date: Tue Nov 29 23:23:30 2016
New Revision: 242982
URL: https://gcc.gnu.org/viewcvs?rev=242982=gcc=rev
Log:
Backported from mainline
2016-11-19 Kaz Kojima
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78549
Jerry DeLisle changed:
What|Removed |Added
Status|NEW |WAITING
Assignee|unassigned
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78426
--- Comment #3 from Kazumoto Kojima ---
Author: kkojima
Date: Tue Nov 29 23:20:28 2016
New Revision: 242981
URL: https://gcc.gnu.org/viewcvs?rev=242981=gcc=rev
Log:
Backported from mainline
2016-11-19 Kaz Kojima
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78576
--- Comment #13 from Breno Leitao ---
(In reply to Bill Schmidt from comment #11)
> Breno, what is your environment? Which glibc is present?
We found this problem originally on Debian[1], but we tested and reproduced it
even on Big Endian
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78590
Segher Boessenkool changed:
What|Removed |Added
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78560
--- Comment #3 from Michael Meissner ---
Unfortunately once you get past the problem with the element being a memory
location, the example does not compile on little endian due to an operand out
of error message from the assembler:
-> ./xgcc
On 11/28/2016 10:33 AM, Andre Vehreschild wrote:
PING!
I know it's a lengthy patch, but comments would be nice anyway.
- Andre
On Tue, 22 Nov 2016 20:46:50 +0100
Andre Vehreschild wrote:
Hi all,
attached patch addresses the need of extending the API of the caf-libs to
enable
On 11/29/2016 03:51 PM, Richard Sandiford wrote:
Jeff Law writes:
On 11/15/2016 09:04 AM, Richard Sandiford wrote:
alias.c encodes memory sizes as follows:
size > 0: the exact size is known
size == 0: the size isn't known
size < 0: the exact size of the reference itself is
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78602
--- Comment #1 from Michael Meissner ---
Created attachment 40195
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=40195=edit
Proposed patch to fix the problem
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78560
--- Comment #2 from Michael Meissner ---
Created attachment 40194
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=40194=edit
Proposed patch to fix the problem
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78560
Michael Meissner changed:
What|Removed |Added
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed|
Jeff Law writes:
> On 11/15/2016 09:04 AM, Richard Sandiford wrote:
>> alias.c encodes memory sizes as follows:
>>
>> size > 0: the exact size is known
>> size == 0: the size isn't known
>> size < 0: the exact size of the reference itself is known,
>> but the address has been
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78605
Martin Sebor changed:
What|Removed |Added
Keywords||diagnostic
On 11/29/2016 09:32 AM, Martin Sebor wrote:
On 11/29/2016 08:38 AM, Gerald Pfeifer wrote:
This took me a bit to get to the bottom of, but I know believe
that we need to work both on the documentation and implementation
of -Wformat-length, in particular when it comes to floats.
#include
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78605
Bug ID: 78605
Summary: bogus -Wformat-length=1 with %f
Product: gcc
Version: 7.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: middle-end
Snapshot gcc-5-20161129 is now available on
ftp://gcc.gnu.org/pub/gcc/snapshots/5-20161129/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 5 SVN branch
with the following options: svn://gcc.gnu.org/svn/gcc/branches/gcc-5
Hello,
On Tue, 29 Nov 2016, Sebastian Huber wrote:
> * env.c: Split out ICV definitions into...
> * icv.c: ...here (new file) and...
> * icv-device.c: ...here. New file.
>
> the env.c contains now only local symbols (at least for target *-rtems*-*):
>
[...]
>
> Thus the
On Tue, Nov 29, 2016 at 2:16 PM, augustine.sterl...@gmail.com
wrote:
> On Tue, Nov 29, 2016 at 2:08 PM, Max Filippov wrote:
>> 2016-11-29 Max Filippov
>> gcc/
>> * config/xtensa/xtensa.c (hwloop_optimize): Don't
On Tue, Nov 29, 2016 at 03:20:08PM -0700, Jeff Law wrote:
> On 11/29/2016 12:41 PM, Jakub Jelinek wrote:
> >The x86_64 stv pass uses PUT_MODE to change REGs and MEMs in place to affect
> >all setters and users, but that is undesirable in debug insns which are
> >intentionally ignored during the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77517
Harald Anlauf changed:
What|Removed |Added
CC||anlauf at gmx dot de
--- Comment #4
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78603
jcmvbkbc at gcc dot gnu.org changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78584
DJ Delorie changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78603
--- Comment #3 from jcmvbkbc at gcc dot gnu.org ---
Author: jcmvbkbc
Date: Tue Nov 29 22:22:13 2016
New Revision: 242979
URL: https://gcc.gnu.org/viewcvs?rev=242979=gcc=rev
Log:
xtensa: Fix PR target/78603
2016-11-29 Max Filippov
On Tue, Nov 29, 2016 at 10:58:35PM +0100, Janus Weil wrote:
>
> here is a rather straightforward patch for an ice-on-invalid
> regression. Regtests cleanly on x86_64-linux-gnu. Ok for trunk?
>
Yes.
--
Steve
On 11/29/2016 12:41 PM, Jakub Jelinek wrote:
Hi!
The x86_64 stv pass uses PUT_MODE to change REGs and MEMs in place to affect
all setters and users, but that is undesirable in debug insns which are
intentionally ignored during the analysis and we should keep using correct
modes (TImode) instead
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78576
--- Comment #12 from Bill Schmidt ---
Ah, I was incorrect about that. If I use -O0, the test produces 26 in my
environment as well. At higher optimization the whole computation is folded.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78601
--- Comment #2 from Bill Seurer ---
That patch indeed seems to fix these problems.
On Tue, Nov 29, 2016 at 2:08 PM, Max Filippov wrote:
> 2016-11-29 Max Filippov
> gcc/
> * config/xtensa/xtensa.c (hwloop_optimize): Don't emit zero
> overhead loop start between a call and its CALL_ARG_LOCATION
> note.
Approved.
On 11/15/2016 09:04 AM, Richard Sandiford wrote:
alias.c encodes memory sizes as follows:
size > 0: the exact size is known
size == 0: the size isn't known
size < 0: the exact size of the reference itself is known,
but the address has been aligned via AND. In this case
"-size" includes the
1 - 100 of 365 matches
Mail list logo