https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67668
--- Comment #4 from BENAÏSSA ---
Thank you for your quick and clear reply .
Note:
I think that using the same symbol operator for doing two different things
can be a potential source of blind errors.
I confirm that this is only a
Hi,
if been working with the windriver Diab c compiler for 32bit ppc for and
encountered an incompatibly with the eabi version of the gcc 4.83. When
calling functions with more than 8 float arguments the gcc stores the 9th
float argument (and so on) as a float where as the diab compiler stores
> + /* Registers that can not be allocated for this allocno, for example
> because
> + there is an ASM_OPERANDS with that register as an output and this pseudo
> + as an earlyclobber input. */
> + HARD_REG_SET forbidden_regs;
You mean "with that register as an earlyclobber output and
On 09/22/2015 01:15 PM, Richard Henderson wrote:
And doesn't it have to be =& and always at the start for an asm constraint?
For operands in patterns, we have to consider operand alternatives, but that's
not on issue here.
Technically we do support alternatives on asms. Not usefully except
On 09/22/15 04:52, David Chisnall wrote:
> On 22 Sep 2015, at 12:47, H.J. Lu wrote:
>>
>> since __builtin_exception_error () is the same as
>> __builtin_return_address (0) and __builtin_interrupt_data () is
>> address of __builtin_exception_error () + size of register.
>
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67684
Jonathan Wakely changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
On 09/22/2015 12:12 PM, Jeff Law wrote:
> On 09/22/2015 12:50 PM, Richard Henderson wrote:
>>
>>> +asm_constraint_earlyclobber (const char *constraint)
>>> +{
>>> + while (*constraint != 0)
>>> +{
>>> + if (*constraint == '&')
>>> +return true;
>>> + ++constraint;
>>> +}
>>>
On 09/22/15 04:44, David Chisnall wrote:
> On 22 Sep 2015, at 12:39, H.J. Lu via cfe-dev wrote:
>>
>> The center piece of my proposal is not to change how parameters
>> are passed in compiler. As for user experience, the feedbacks on
>> my proposal from our users are very
On 09/21/2015 05:31 AM, Dominik Vogt wrote:
This patch adds to new backend hooks
ASM_OUTPUT_START_FUNCTION_HEADER and
ASM_OUTPUT_END_FUNCTION_FOOTER that may be defined to emit
assembly code at the very start or end of a function. This
functionality is needed by the patch that ports the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59124
--- Comment #32 from baoshan ---
(In reply to Manuel López-Ibáñez from comment #30)
> (In reply to baoshan from comment #29)
> > > However, it is clear that _14 = baz[_9] is executed only 5 times (not 5
> > > times + 1). Why is this estimate
Not unlike what we've seen in other ports. The PA backend left-shifts a
negative number invoking undefined behaviour.
This patch avoids the warning for undefined behaviour and presumably
would allow the PA port to bootstrap again.
Tested with the various PA crosses listed in
On 09/22/2015 12:50 PM, Richard Henderson wrote:
+asm_constraint_earlyclobber (const char *constraint)
+{
+ while (*constraint != 0)
+{
+ if (*constraint == '&')
+ return true;
+ ++constraint;
+}
+ return false;
+}
This would be
return strchr (constraint, '&')
On 09/21/2015 07:25 AM, Bernd Schmidt wrote:
On 08/27/2015 01:18 PM, Evgeny Stupachenko wrote:
Based on RFC:
https://gcc.gnu.org/ml/gcc-patches/2015-08/msg01322.html
The patch implement an extension to Function Multiversioning that
allows to clone a function for multiple targets.
On 09/22/15 01:41, David Chisnall wrote:
> On 21 Sep 2015, at 21:45, H.J. Lu via cfe-dev wrote:
>>
>> The main purpose of x86 interrupt attribute is to allow programmers
>> to write x86 interrupt/exception handlers in C WITHOUT assembly
>> stubs to avoid extra branch from
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67684
Bug ID: 67684
Summary: [concepts] friend access not working with constrained
function
Product: gcc
Version: 6.0
Status: UNCONFIRMED
Severity: normal
On 09/22/2015 12:18 PM, Jeff Law wrote:
> On 09/22/2015 01:15 PM, Richard Henderson wrote:
>>> And doesn't it have to be =& and always at the start for an asm constraint?
>>> For operands in patterns, we have to consider operand alternatives, but
>>> that's
>>> not on issue here.
>>
>>
Hi,
today I noticed that the accepts-invalid half this bug report is already
fixed in 5+, but the rejects-valid second half is still an issue: I
think we can easily use CLASSTYPE_IS_TEMPLATE on current_class_type to
skip members of non-template classes. Tested x86_64-linux.
Thanks,
Paolo.
On 09/22/2015 07:36 AM, Kyrill Tkachov wrote:
Hi all,
Unfortunately, I see a testsuite regression with this patch:
FAIL: gcc.dg/pr66299-2.c scan-tree-dump-not optimized "<<"
The reduced part of that test is:
void
test1 (int x, unsigned u)
{
if ((1U << x) != 64
|| (2 << x) != u
On 09/22/2015 01:20 PM, Richard Henderson wrote:
On 09/22/2015 12:18 PM, Jeff Law wrote:
On 09/22/2015 01:15 PM, Richard Henderson wrote:
And doesn't it have to be =& and always at the start for an asm constraint?
For operands in patterns, we have to consider operand alternatives, but that's
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67677
Bug ID: 67677
Summary: [6 Regression] r226005 causes "Conditional jump or
move depends on uninitialised value(s)"
Product: gcc
Version: 6.0
Status: UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67666
vries at gcc dot gnu.org changed:
What|Removed |Added
Keywords||patch
--- Comment #3 from
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67649
--- Comment #10 from Markus Trippelsdorf ---
A gave your patch a quick spin on gcc112 (compile farm machine).
It fixes the issue.
On 2015/9/18 04:02 PM, Jakub Jelinek wrote:
> On Fri, Sep 18, 2015 at 03:41:30PM +0800, Chung-Lin Tang wrote:
>> this patch fixes the uninitialized acc_device_lock mutex situation
>> reported in PR 67141. The patch attached on the bugzilla page
>> tries to solve it by constructor priorities, which
On Tue, Sep 22, 2015 at 02:49:04PM +0800, Chung-Lin Tang wrote:
> Committed, thanks for the review.
> I believe this patch is also needed for 5.x, okay for that branch as well?
Ok.
Jakub
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67598
--- Comment #1 from Arseny Solokha ---
(In reply to Arseny Solokha from comment #0)
> I still have to find out
> when the issue have started showing up, given that I now have half a year
> wide window.
6.0.0-alpha20150802 snapshot bootstraps
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67141
--- Comment #6 from Chung-Lin Tang ---
Author: cltang
Date: Tue Sep 22 06:45:22 2015
New Revision: 227994
URL: https://gcc.gnu.org/viewcvs?rev=227994=gcc=rev
Log:
2015-09-22 Chung-Lin Tang
PR libgomp/67141
Hi,
Consider this test-case:
struct ps
{
int *__restrict__ p;
};
void
f (struct ps &__restrict__ ps1)
{
*(ps1.p) = 1;
}
Atm, the restrict on p has no effect. Now, say we add a field to the struct:
struct ps
{
int *__restrict__ p;
int a;
};
Then the restrict on p does have the
Use find_opt instead of linear search through options in
handle_pragma_diagnostic (PR 49654) and reject non-warning options and
options not valid for the current language (PR 49655).
Boot on x86_64-linux-gnu.
OK?
gcc/testsuite/ChangeLog:
2015-09-22 Manuel López-Ibáñez
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67680
Marek Polacek changed:
What|Removed |Added
Status|UNCONFIRMED |WAITING
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67682
Bug ID: 67682
Summary: Missed vectorization: (another) straight-line
memcpy/memset not vectorized when equivalent loop is
Product: gcc
Version: 6.0
Status: UNCONFIRMED
On Tue, Sep 22, 2015 at 11:29 AM, Richard Henderson wrote:
>> @@ -10398,11 +10411,13 @@ output_line_info (bool prologue_only)
>>ASM_GENERATE_INTERNAL_LABEL (p1, LN_PROLOG_AS_LABEL, 0);
>>ASM_GENERATE_INTERNAL_LABEL (p2, LN_PROLOG_END_LABEL, 0);
>>
>> +#ifndef
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67679
Dominique d'Humieres changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67680
Bug ID: 67680
Summary: Seg Fault in gcc 4.9.3 compiling
libiberty/floatformat.c when building gcc 5.2.1 on
Cygwin 64 on Windows
Product: gcc
Version: 4.9.3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67681
Bug ID: 67681
Summary: Missed vectorization: induction variable used after
loop
Product: gcc
Version: 6.0
Status: UNCONFIRMED
Severity: normal
On 09/22/2015 11:49 AM, Jason Merrill wrote:
On 09/16/2015 10:24 AM, Andres Tiraboschi wrote:
Hi, this patch fix the following bug:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67064 for gcc 5.2
It passes all the gcc tests except for this:
FAIL: g++.dg/cpp1y/auto-fn15.C -std=gnu++14 (test for
Marcus Shawcroft writes:
> On 26 August 2015 at 14:58, Jiong Wang wrote:
>>
>> This patch cover tlsle tiny model tests, tls size truncation for tiny &
>> small model included also.
>>
>> All testcases pass native test.
>>
>> OK for trunk?
>>
>> 2015-08-26 Jiong Wang
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67667
--- Comment #2 from BENAÏSSA ---
Thank you for your quick and clear reply .
Note:
I think that using the same symbol operato as GNU extension for doing two
different things
can be a potential source of blind errors .
I confirm that
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61578
Dominik Vogt changed:
What|Removed |Added
CC||vogt at linux dot vnet.ibm.com
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67391
Oleg Endo changed:
What|Removed |Added
CC||kkojima at gcc dot gnu.org
--- Comment #1
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53856
Paolo Carlini changed:
What|Removed |Added
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61578
--- Comment #28 from Dominik Vogt ---
Created attachment 36371
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=36371=edit
Outpout of the reload pass (BAD)
The full output of the reload pass on S/390, showing the behaviour described in
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65405
Manuel López-Ibáñez changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
Am 22.09.2015 um 19:43 schrieb David Edelsohn:
On Tue, Sep 22, 2015 at 1:39 PM, Bernhard Schommer
wrote:
Hi,
if been working with the windriver Diab c compiler for 32bit ppc for and
encountered an incompatibly with the eabi version of the gcc 4.83. When
calling
On 09/21/2015 04:03 PM, Hal Finkel wrote:
> - Original Message -
>> From: "H.J. Lu"
>> To: "Hal Finkel"
>> Cc: "GCC Development" , cfe-...@lists.llvm.org
>> Sent: Monday, September 21, 2015 5:57:36 PM
>> Subject: Re: [cfe-dev] RFC:
On Tue, 2015-09-22 at 17:53 +0200, Bernd Schmidt wrote:
> On 09/22/2015 03:35 PM, Oleg Endo wrote:
> > On SH, the result of comparisons etc. is stored in the T_REG. It's a 1
> > bit reg but described as SImode. To get the T_REG into another reg,
> > there's this insn:
> >
> > (define_insn "movt"
On Mon, Jul 13, 2015 at 05:44:59PM -0700, Paul E. McKenney wrote:
> On Tue, May 19, 2015 at 05:55:10PM -0700, Paul E. McKenney wrote:
> > Hello!
> >
> > Following up on last year's discussion (https://lwn.net/Articles/586838/,
> > https://lwn.net/Articles/588300/), I believe that we have a
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67683
Bug ID: 67683
Summary: Missed vectorization: shifts of an induction variable
Product: gcc
Version: 6.0
Status: UNCONFIRMED
Keywords: missed-optimization
Severity: normal
On Tue, Sep 22, 2015 at 1:39 PM, Bernhard Schommer
wrote:
> Hi,
>
> if been working with the windriver Diab c compiler for 32bit ppc for and
> encountered an incompatibly with the eabi version of the gcc 4.83. When
> calling functions with more than 8 float arguments
On Wed, 2015-09-23 at 00:48 +0900, Oleg Endo wrote:
> I haven't checked the details. But I guess because expand_binop wants
> to somehow reuse the input and output it creates a DImode pseudo, puts
> the input there, does the DImode plus and the returned "target" is a
> SImode subreg of the
This is v2 of this patch; an earlier version was sent as:
https://gcc.gnu.org/ml/gcc-patches/2015-09/msg00737.html
Thanks for the comments so far.
Changes in v2:
* Added a big descriptive comment for class rich_location in
libcpp/include/line-map.h.
* Implemented x-offset support for very
This is a combination of various patches from v1 of the kit,
including:
12/22: Add source-ranges for trees
13/22: gcc-rich-location.[ch]: add methods for working with tree ranges
14/22: C: capture tree ranges for various expressions
The implementation of how ranges are stored has completely
On 09/22/2015 09:41 PM, Jeff Law wrote:
Essentially it allows us to more easily support
per-microarchitecture-optimized versions of functions. You list just
have to list the microarchitectures and the compiler handles the rest.
Very simple, very easy. I'd think it'd be particularly helpful
This is an updated version of this patch kit:
https://gcc.gnu.org/ml/gcc-patches/2015-09/msg00726.html
It's still at the level of an RFC/work-in-progress; I'm posting for
feedback rather than for formal approval at this time (though the
first two patches are perhaps ready).
For the sake of
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67688
Bug ID: 67688
Summary: [MinGW/Cygwin] Attributes selectany and section cannot
be used together
Product: gcc
Version: 5.2.1
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67391
--- Comment #3 from Kazumoto Kojima ---
(In reply to Oleg Endo from comment #1)
> Kaz, do you have any memory of the extra checks? Isn't it enough to just
> accept the addsi3 pattern as "rC = rA + {rB|imm}" and insert the reg-reg
> copy after
-multilib
Thread model: posix
gcc version 6.0.0 20150922 (experimental) [trunk revision 228013] (GCC)
$
$ gcc-trunk -O0 small.c; ./a.out
$ gcc-5.2 -O1 small.c; ./a.out
$
$ gcc-trunk -O1 small.c
$ ./a.out
Aborted
$
--
int a, b, c = 1, d, e;
void
fn1 ()
{
e
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67391
--- Comment #4 from Oleg Endo ---
(In reply to Kazumoto Kojima from comment #3)
>
> Ugh, those checks look just wrong and I can't remind why I've
> added them. 33707 didn't do that and checked overlapping at
> the split condition only.
We currently correctly emit a -Wmisleading-indentation warning for the
code
...
if (flagB);
{
foo ();
}
but we fail to emit a warning for the syntactically similar code
...
else if (flagB);
{
foo ();
}
because in the heuristic in question we are inspecting the column of
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67391
--- Comment #5 from Kazumoto Kojima ---
(In reply to Oleg Endo from comment #4)
> I've just checked, the code is also present in GCC 5. Because of the funny
> side effects even with LRA disabled (this PR) I'd like to backport this to
> the GCC
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67649
--- Comment #11 from Mikhail Maltsev ---
Author: miyuki
Date: Wed Sep 23 02:31:14 2015
New Revision: 228033
URL: https://gcc.gnu.org/viewcvs?rev=228033=gcc=rev
Log:
Fix use of valgrind API
gcc/
PR middle-end/67649
*
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67649
--- Comment #12 from Mikhail Maltsev ---
(In reply to Markus Trippelsdorf from comment #10)
> A gave your patch a quick spin on gcc112 (compile farm machine).
> It fixes the issue.
Thanks, Markus. I committed the fix.
Hi all.
Pool allocators use valgrind API to mark freed memory blocks as unaccessible.
Shared memory block pool needs to make them accessible again before returning to
other pools (otherwise valgrind will cry wolf).
I checked that build passes without valgrind checks and starts fine (i.e. errors
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67391
--- Comment #2 from Oleg Endo ---
Created attachment 36373
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=36373=edit
Proposed patch
Tested on sh-elf, LRA enabled, with make -k check
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67192
--- Comment #12 from Patrick Palka ---
(In reply to Manuel López-Ibáñez from comment #10)
> (In reply to Manuel López-Ibáñez from comment #8)
> > Does GCC work at all if input_location is saved and restored in
> > c_parser_peek_token? I guess
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55815
--- Comment #5 from felix-glibc at fefe dot de ---
How about you add SipHash and make it selectable at runtime.
Then I can file security bugs against all relevant programs not
selecting it for being vulnerable and glibc has their ass covered
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67690
Bug ID: 67690
Summary: wrong code with -O2 on x86_64/Linux
Product: gcc
Version: 5.2.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67690
--- Comment #1 from Erik Volk ---
Created attachment 36375
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=36375=edit
full output from gcc -v
This patch adds a test plugin that recurses down an expression tree,
printing diagnostics showing the ranges of each node in the tree.
It corresponds to:
[PATCH 15/22] Add plugin to recursively dump the source-ranges in a tree
https://gcc.gnu.org/ml/gcc-patches/2015-09/msg00741.html
from v1
This patch is essentially identical to v1 here:
https://gcc.gnu.org/ml/gcc-patches/2015-09/msg00729.html
The only change is in the ChangeLog, moving the libgo.exp
ChangeLog entry into gcc/testsuite/ChangeLog, analogous to
where Ian put it when introducing the file in r167407.
OK for trunk?
This is an updated version of:
https://gcc.gnu.org/ml/gcc-patches/2015-09/msg00736.html
Changes in V2 of the patch:
* c_lex_with_flags: don't write through the range ptr if it's NULL
* don't add any fields to the C++ frontend's cp_token for now
* libcpp/lex.c: prevent usage of
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59124
--- Comment #33 from Manuel López-Ibáñez ---
(In reply to baoshan from comment #32)
> And I think it is not wrong, it's just inaccurate, and it is not making any
> wrong result in running time.
>
> Can you point me how to proceed?
To be
On Tue, Sep 22, 2015 at 11:11:47AM -0500, Segher Boessenkool wrote:
> > So, given that your solution seems to work, the patch is ok.
>
> Thanks! Here is what I will commit after bootstrap+test (the superfluous
> assert removed, and the comment for the code quoted above tweaked a bit).
I added
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67685
Bug ID: 67685
Summary: ICE on invalid requires expression
Product: gcc
Version: c++-concepts
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Actually, I was trying to reject non-warning options as argument to
-Werror=. However, the new test fails because -fdiagnostics-color=never is
always placed by the driver after the warning options when calling the compiler
proper. This patch prunes all -fdiagnostics-color from the command-line but
On 09/22/2015 06:26 AM, Marek Polacek wrote:
On Mon, Sep 21, 2015 at 07:06:01PM +0200, Marek Polacek wrote:
I realized that current patch has a minor deficiency: it will start
a chain even in case the first condition has a side-effect thus the
chain should be invalid. I'll fix this problem
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=48885
vries at gcc dot gnu.org changed:
What|Removed |Added
CC||rguenth at gcc dot gnu.org,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55815
Geoff Pike changed:
What|Removed |Added
CC||gpike at google dot com
--- Comment #4
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67604
Segher Boessenkool changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55815
Mikhail Maltsev changed:
What|Removed |Added
CC||miyuki at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67692
Bug ID: 67692
Summary: [concepts] ICE when using requires in non-concept
contexts
Product: gcc
Version: 6.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67680
Brian Plummer changed:
What|Removed |Added
CC||bplummer at hotmail dot com
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67680
--- Comment #3 from Brian Plummer ---
As requested.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67691
Bug ID: 67691
Summary: [SH] Omit zero extension of shift amounds for dynamic
shifts
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
On Tue, Sep 22, 2015 at 07:39:43PM +0200, Bernhard Schommer wrote:
> Does anyone know the reason why the gcc passes the argument as single float?
That's how the first powerpc gcc implementation behaved. Once gcc
compiled code is out in the field, you need to ask everyone to
recompile their code
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67680
--- Comment #4 from Brian Plummer ---
I had these comments in my message, but they got lost when I added my
attachment.
floatformat.preprocessed.c was created with this command :
Brian@MBPWin7-64 ~/gnu/gcc/gcc-5.2.0/libiberty
$ gcc -E -c
Thank you for the review.
The patch still works with gcc 5, but the fail reproduced on trunk
(looks like it appeared while patch was at review). I'll debug it and
fix.
As a workaround to test the feature...
Removing
"gimple_call_set_fndecl (call, idecl);" from multiple_target.c
should resolve the
On 09/22/2015 02:02 PM, Thomas Schwinge wrote:
gcc/
* gcc.c (handle_foffload_option): Don't lose the trailing NUL
character when appending to offload_targets.
gcc/
* configure.ac (offload_targets, OFFLOAD_TARGETS): Separate
offload targets by
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67321
Ramana Radhakrishnan changed:
What|Removed |Added
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed|
This is a modified version of the previous patch that removes the
documentation and read-md.c fixes. These patches have been submitted
separately and approved.
This patch is designed to address code that was not being vectorized due
to missing widening patterns in the ARM backend. Code such
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66454
Patrick Palka changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
CC|
I advise looking at the "Power Architecture® 32-bit Application Binary
Interface Supplement 1.0 - Embedded", not any older EABI documents.
There may well be bugs in this ABI document (i.e. it may fail to reflect
actual practice), but it's still more reliable as a guide to current
practice
Snapshot gcc-5-20150922 is now available on
ftp://gcc.gnu.org/pub/gcc/snapshots/5-20150922/
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
Currently, the gimplifier will incorrectly create implicit firstprivate
mappings for pointer variables. That's fine except when the pointer
points to a dummy argument. In which case, the gimplifier should check
the type of the value being pointed to before deciding on the type of
implicit mapping.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67686
Bug ID: 67686
Summary: [concepts] segfault in finish_call_expr function
Product: gcc
Version: 6.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66755
Ramana Radhakrishnan changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67687
Bug ID: 67687
Summary: [c++0x][constexpr] initialize constexpr member with
constexpr constructor
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity:
On 21 September 2015 at 15:38, James Greenhalgh
wrote:
> ---
> gcc/
>
> 2015-09-21 James Greenhalgh
>
> * config/aarch64/aarch64-simd.md
>
> (aarch64_float_truncate_hi_v4sf): Rewrite as an expand.
>
When using an asm register variable as an input or output operand for an
inline assembler block, GCC guarantees that the specified register is
used for the operand in question (see
https://gcc.gnu.org/onlinedocs/gcc/Local-Reg-Vars.html). Together with
earlyclobber constraints
On 09/22/2015 03:35 PM, Oleg Endo wrote:
On SH, the result of comparisons etc. is stored in the T_REG. It's a 1
bit reg but described as SImode. To get the T_REG into another reg,
there's this insn:
(define_insn "movt"
[(set (match_operand:SI 0 "arith_reg_dest" "=r")
On Tue, Sep 22, 2015 at 05:47:25PM +0200, Bernd Schmidt wrote:
> On 09/21/2015 04:01 PM, Segher Boessenkool wrote:
> >On Mon, Sep 21, 2015 at 01:56:28PM +0200, Bernd Schmidt wrote:
> >>>+ basic_block new_bb = create_empty_bb (EXIT_BLOCK_PTR_FOR_FN
> >>>(cfun)->prev_bb);
> >>>+ BB_COPY_PARTITION
1 - 100 of 196 matches
Mail list logo