On January 14, 2015 5:23:21 PM CET, Ilya Enkovich
wrote:
>On 14 Jan 15:35, Richard Biener wrote:
>> On Wed, Jan 14, 2015 at 3:28 PM, Ilya Enkovich
> wrote:
>> > Hi,
>> >
>> > SRA gimple passes may add loads to functions with no SSA update.
>Later it causes ICE when function with not updated SSA
On Thu, Jan 8, 2015 at 12:33 PM, Patrick Wollgast
wrote:
> A short recap again:
>
> Latest patch, changelog and a test program (further information about
> the program in the mail):
> https://gcc.gnu.org/ml/gcc-patches/2014-11/msg03368.html
In that patch, the change to varasm.c looks wrong if nei
Hello!
> This patch adds support to the GCC tree for building tools that are
> used with Go. There are two external used tools (go, gofmt) and one
> tool used internally by go (cgo). This patch is pure machinery, with
> no source code. The tools are not built by default, only when go is
> enabl
Hi Vladimir,
An issue has been identified with LRA when running CPU2006 h264ref benchmark.
I'll try to describe what the issue is and a fix applied as it is very
difficult to reproduce it and it is next to impossible to create a narrowed
testcase on top of the source code restrictions.
The conce
Robert Suchanek writes:
> Here is the revised patch that would handle the other cases as per Richard's
> comments.
>
> I slightly modified Matthew's proposed patch and used split_const
> instead of get_related_value. AFAICS, the canonical form would always have
> the 'plus' expression.
>
> The off
Hi Matthew,
> -Original Message-
> From: Matthew Fortune [mailto:matthew.fort...@imgtec.com]
> Sent: Tuesday, January 06, 2015 7:43 AM
> To: Moore, Catherine
> Cc: 'gcc-patches@gcc.gnu.org' (gcc-patches@gcc.gnu.org)
> Subject: [MIPS] Update the ZC constraint for MIPSR6 and use it
>
> Upda
"Maciej W. Rozycki" writes:
> On Wed, 14 Jan 2015, Richard Sandiford wrote:
>
>> > Taking care that the default compilation mode does not conflict (e.g.
>> > MIPS16, incompatible) and taking any exceptions into account (e.g. n64,
>> > unsupported) I presume, right?
>>
>> mips.exp sorts that ou
Moore, Catherine writes
> Hi Matthew,
>
> > -Original Message-
> > From: Matthew Fortune [mailto:matthew.fort...@imgtec.com]
> > Sent: Tuesday, January 06, 2015 7:43 AM
> > To: Moore, Catherine
> > Cc: 'gcc-patches@gcc.gnu.org' (gcc-patches@gcc.gnu.org)
> > Subject: [MIPS] Update the ZC c
There were some -fcompare-debug regressions when I removed the
deferred_asm_name auxiliary data structure from dwarf2out. Jason was
kind enough to tackle them (or at least the main one).
Apparently there was some bug in the mangling code that necessitated the
entire deferred_asm_name vector.
> -Original Message-
> From: Matthew Fortune [mailto:matthew.fort...@imgtec.com]
> Sent: Wednesday, January 14, 2015 2:54 PM
> To: Moore, Catherine
> Cc: 'gcc-patches@gcc.gnu.org' (gcc-patches@gcc.gnu.org)
> Subject: RE: [MIPS] Update the ZC constraint for MIPSR6 and use it
>
> Moore, Ca
Richard Sandiford writes:
> "Maciej W. Rozycki" writes:
> > On Wed, 14 Jan 2015, Richard Sandiford wrote:
> >> I think we just have to accept that there are so many possible
> >> combinations that we can't test everything that's potentially
> relevant.
> >> I think it's more useful to be flexible
Moore, Catherine writes:
> > -Original Message-
> > From: Matthew Fortune [mailto:matthew.fort...@imgtec.com]
> > Sent: Wednesday, January 14, 2015 2:54 PM
> > To: Moore, Catherine
> > Cc: 'gcc-patches@gcc.gnu.org' (gcc-patches@gcc.gnu.org)
> > Subject: RE: [MIPS] Update the ZC constraint
On 14.01.2015 20:00, Ian Lance Taylor wrote:
> On Thu, Jan 8, 2015 at 12:33 PM, Patrick Wollgast
> wrote:
>> A short recap again:
>>
>> Latest patch, changelog and a test program (further information about
>> the program in the mail):
>> https://gcc.gnu.org/ml/gcc-patches/2014-11/msg03368.html
>
The PPC64LE ABI specifies POWER8 ISA as the minimum hardware
requierment. Currently, Linux distributions are building the
toolchain using --with-cpu=power7 or power8, as they wish. GCC
defaults to essentially the POWER4 ISA.
The appended patch changes the default for PPC64LE to POWER8 (ISA
2.7).
On 01/14/15 13:32, David Edelsohn wrote:
The PPC64LE ABI specifies POWER8 ISA as the minimum hardware
requierment. Currently, Linux distributions are building the
toolchain using --with-cpu=power7 or power8, as they wish. GCC
defaults to essentially the POWER4 ISA.
The appended patch changes t
On 01/14/15 00:48, Martin Uecker wrote:
If you plan to contribute regularly, you should go ahead and apply for
write access to the repository so that you'll be able to commit your own
patches once they're approved.
I put a request in with you as sponsor (hope this is ok).
Of course.
You'
On 01/14/2015 10:08 AM, Paolo Carlini wrote:
I can look again, but as far as I remember nothing is clearing it, it
just stay false because the ICE happens while we process the 'i' on the
right hand side and the DECL_INITIALIZED_P becomes true only in
cp_finish_decl.
Ah, please say that in the c
On 01/14/2015 11:28 AM, Patrick Palka wrote:
Second, since the user probably intended to
have written an explicit template instantiation (as in the PR), the FE
should suggest adding "template" before such a declaration, that is the
declaration
struct X<5>; // error + suggest adding "templat
On 01/14/2015 01:28 PM, Joseph Myers wrote:
On Wed, 14 Jan 2015, Andrew MacLeod wrote:
- There is a warning for invalid memory models already, so I just continued
using that.
- I remove the check for CONSUME in exchange since the current standard makes
no mention of that being illegal.
- I also
On 01/14/2015 12:30 AM, Jan Hubicka wrote:
I would like to ping the patch to fix divergence between a type and its main
variant introduced by C++ FE.
OK.
Jason
On 01/14/15 10:10, Robert Suchanek wrote:
Here is the revised patch that would handle the other cases as per Richard's
comments.
I slightly modified Matthew's proposed patch and used split_const
instead of get_related_value. AFAICS, the canonical form would always have
the 'plus' expression.
Th
On 01/14/15 04:38, H.J. Lu wrote:
On Tue, Jan 13, 2015 at 11:15 PM, Jeff Law wrote:
On 01/13/15 14:27, H.J. Lu wrote:
-fprofile -mfentry works with PIE if gcrt1.o is compiled with -fPIC. A
glibc has been filed, PR 17836, and a glibc patch has been submitted.
OK for trunk?
Thanks.
H.J.
--
On 01/14/15 04:27, Venkataramanan Kumar wrote:
Hi all,
When trying to debug GCC combiner pass with the test case in PR63949
ref https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63949 I came across this code.
This code in "make_compound_operation" assumes that all PLUS and MINUS
RTX are "MEM" type f
On 01/14/15 03:54, Matthew Wahab wrote:
Hello,
Test case g++.dg/torture/20141013.C (added
https://gcc.gnu.org/ml/gcc-patches/2014-10/msg01190.html) triggers the
warning
--
20141013.C:45:23: warning: width of 'tree_base::code' exceeds its type
--
on arm-none-eabi.
The code specifies a bitfiel
I tried compiling an empty plugin that just included gcc-plugin.h and
plugin-version.h and found that these header files were included from
gcc-plugin.h but not in the list of header files to be copied to the
plugin include directory.
OK to checkin?
Steve Ellcey
sell...@imgtec.com
2015-01-14 St
On 12/10/14 06:47, Segher Boessenkool wrote:
On Tue, Dec 09, 2014 at 12:15:30PM -0700, Jeff Law wrote:
@@ -3323,7 +3396,11 @@ try_combine (rtx_insn *i3, rtx_insn *i2, rtx_insn
*i1, rtx_insn *i0,
rtx old = newpat;
total_sets = 1 + extra_sets;
newpat = gen_rtx_PARALLE
Hi!
This pulls libiberty.h's copyright update from Binutils, so that the
file is synced again.
2015-12-14 Jan-Benedict Glaw
* libiberty.h: Merge Copyright year update from Binutils.
diff --git a/include/ChangeLog b/include/ChangeLog
index dbf2554..c1011b9 100644
--- a/incl
On 11/14/14 13:41, Kai Tietz wrote:
Hello,
this patch fixes some potential warnings for C++ bootstrap. I noticed
them while working on the delayed folding for C++-FE on boostrap.
ChangeLog
2014-11-14 Kai Tietz
* dwarf2out.c(output_loc_operands): Make sure that
comparison is done
On Wed, Jan 14, 2015 at 4:28 PM, Jason Merrill wrote:
> On 01/14/2015 11:28 AM, Patrick Palka wrote:
>>
>> Second, since the user probably intended to
>> have written an explicit template instantiation (as in the PR), the FE
>> should suggest adding "template" before such a declaration, that is th
A few months ago I posted the "porting to" document for GCC 5.
But I never got around to commit it, so here it is again, this
time with feewing. I fixed description of GNU89 "extern inline",
added some more snippets, and mentioned -Wc9?-c??-compat warnings.
I plan to commit this tomorrow.
--- po
On 12 Jan 14:30, Jeff Law wrote:
> On 01/11/15 12:26, Ilya Verbin wrote:
> >On 09 Jan 10:29, Thomas Schwinge wrote:
> >>As this was the only use of ENABLE_LTO in the testsuite, I suggest to
> >>also remove it from the gcc/Makefile.in:site.exp rule.
> >
> >Done.
> >Here is an updated and retested pa
On 01/14/2015 03:27 AM, Venkataramanan Kumar wrote:
>next_code = (code == MEM ? MEM
>: ((code == PLUS || code == MINUS)
> - && SCALAR_INT_MODE_P (mode)) ? MEM
> + && SCALAR_INT_MODE_P (mode)
> + && (in_code == MEM)) ? MEM
>
On 13/01/15 21:45, Jeff Law wrote:
On 01/09/15 06:39, Jiong Wang wrote:
the bug testcase is
===
typedef short U __attribute__((may_alias, aligned (1)));
struct S
{
_Complex float d __attribute__((aligned (8)));
};
void bar(struct S);
void f5 (int x)
{
struct S s;
(
> -Original Message-
> From: Matthew Fortune [mailto:matthew.fort...@imgtec.com]
> Sent: Monday, January 12, 2015 10:35 AM
> To: Moore, Catherine
> Cc: 'gcc-patches@gcc.gnu.org' (gcc-patches@gcc.gnu.org)
> Subject: [PATCH,MIPS] Add support for the R6 LSA and DLSA instructions
>
> This pa
On 12/15/2014 07:36 AM, Jiong Wang wrote:
> + char buf[64];
> + uint64_t val = ((uint64_t) 1) << UINTVAL (operands[1]);
> + sprintf (buf, "tst\t%%0, %"PRId64, val);
> + output_asm_insn (buf, operands);
> + return "\t%l2";
Better to simply modify the operand, as in
operands[1
I noticed that -fuse-ld= was incorrectly classified as an optimization
option in the manual. It's a driver-only option so it seems better to
list it with the linker options. I've checked in this patch to move it
(there's no change to the actual content of the documentation, just its
location)
Hi
Not a huge patch. Just changes "developement" to "development" in a
comment and error message. The larger issue is that it is in the top level
configure.ac. :)
OK to comment and where?
2015-01-14 Joel Sherrill
* configure.ac: Fix spelling error.
* configure: Regenerate.
--
Joel S
On Wed, Jan 14, 2015 at 12:28 PM, Patrick Wollgast
wrote:
> On 14.01.2015 20:00, Ian Lance Taylor wrote:
>> On Thu, Jan 8, 2015 at 12:33 PM, Patrick Wollgast
>> wrote:
>>> A short recap again:
>>>
>>> Latest patch, changelog and a test program (further information about
>>> the program in the mai
The problem of unexpected code generation is discussed on
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64110
The following patch introduces 2 new constraints '^' and '$' which
are analogous to '?' and '!' but disfavor given alternative when *the
operand with the new constraint* needs a re
On Mon, Jan 12, 2015 at 8:34 AM, Richard Henderson wrote:
> Upstream libffi has added support for Go closures (using the static chain),
> and support for complex numbers. Perhaps less relevant is new support for
> arc, microblaze, moxie, nios, and or1k targets.
>
> Without additional changes for
Hi,
The attached patch fixes a wrong-code issue which was the result of the
initial fix for PR 53988.
Tested with
make -k check RUNTESTFLAGS="--target_board=sh-sim
\{-m2/-ml,-m2/-mb,-m2a/-mb,-m4/-ml,-m4/-mb,-m4a/-ml,-m4a/-mb}"
and no new failures. Committed as 219623. Backports to 4.8 and 4.9
wi
I've committed a patch to libgo to update it to the Go 1.4 release,
except for the runtime package. Much of the runtime package was
rewritten in Go, and it does not really affect users of the library,
so I've postponed that complex merge. All the other packages are
updated. A few minor compiler
> -Original Message-
> From: Matthew Fortune [mailto:matthew.fort...@imgtec.com]
> Sent: Monday, January 12, 2015 11:12 AM
> To: Moore, Catherine
> Cc: 'gcc-patches@gcc.gnu.org' (gcc-patches@gcc.gnu.org)
> Subject: [PATCH,MIPS] Remove all excess parallel constructs
>
> * config/mip
On 01/14/2015 05:04 PM, Patrick Palka wrote:
Did this define a specialization too:
struct X<5> { };
Yes. There's an example in the ARM that says
A class can be defined as the definition of a template class. For example,
template class stream { /* ... */ };
class stream { /* ... */
Somehow two files were omitted from the last commit upgrading to 1.4.
This adds them. Committed to mainline.
Ian
Index: libgo/go/crypto/tls/testdata/Server-TLSv12-IssueTicketPreDisable
===
--- libgo/go/crypto/tls/testdata/Server-TLSv
This patch bumps the version number of libgo, giving it a new soname.
Bootstrapped on x86_64-unknown-linux-gnu. Committed to mainline.
Ian
diff -r 530a9509c45c -r bdf59f9cfda8 libgo/configure.ac
--- a/libgo/configure.acWed Jan 14 16:11:24 2015 -0800
+++ b/libgo/configure.acWed Jan
As the existing comment explains, we should always promote function
arguments and return values. However, notwithstanding its name,
default_promote_function_mode_always_promote does not always promote.
Importantly, it does not for libcalls. This makes ftrapv-[12].c fail
with 64-bit ABIs.
This pa
UNITS_PER_WORD is 8 with -m32 -mpowerpc64. Promoting items smaller
than 8 bytes to 4 bytes doesn't make sense.
I tried to fix it the other way around first, promoting everything
smaller than UNITS_PER_WORD to word_mode; this fails all over the
place, because word_mode is bigger than Pmode. So le
Some hooks return word_mode by default, which is incorrect for -m32
-mpowerpc64. This patch creates a new function rs6000_abi_word_mode
to implement these hooks, and does so.
This fixes 163 testuite FAILs.
[ David already OKed this fixed version, but sending it again is easier
for me. Lazy, e
This fixes 88 testsuite FAILs.
-mpowerpc64 does not change the ABI, but it does change the value of
UNITS_PER_WORD. This code is for 32-bit only so we can use
MIN_UNITS_PER_WORD instead.
Bootstrapped and tested as usual. Okay for mainline?
Segher
2015-01-14 Segher Boessenkool
gcc/
This fixes 141 FAILs.
-mpowerpc64 does not change the ABI, but default_scalar_mode_supported_p
does not know that, and allows TImode for -m32 -mpowerpc64.
This fixes it. Okay for mainline?
2015-01-14 Segher Boessenkool
gcc/
* config/rs6000/rs6000.c (rs6000_scalar_mode_supported_p):
On 01/14/15 15:31, Jiong Wang wrote:
agree, and I think the truncation is needed otherwise there may have ICE
on some target.
and I found current gcc LOCATION info is very good !
have done an experimental hack on at "expand_assignment": 4931 where the
tree is expanded,
gcc could give quite usef
On Wed, Jan 14, 2015 at 8:14 PM, Segher Boessenkool
wrote:
> As the existing comment explains, we should always promote function
> arguments and return values. However, notwithstanding its name,
> default_promote_function_mode_always_promote does not always promote.
> Importantly, it does not for
On Wed, Jan 14, 2015 at 8:14 PM, Segher Boessenkool
wrote:
> UNITS_PER_WORD is 8 with -m32 -mpowerpc64. Promoting items smaller
> than 8 bytes to 4 bytes doesn't make sense.
>
> I tried to fix it the other way around first, promoting everything
> smaller than UNITS_PER_WORD to word_mode; this fai
On Wed, Jan 14, 2015 at 8:14 PM, Segher Boessenkool
wrote:
> This fixes 88 testsuite FAILs.
>
> -mpowerpc64 does not change the ABI, but it does change the value of
> UNITS_PER_WORD. This code is for 32-bit only so we can use
> MIN_UNITS_PER_WORD instead.
>
> Bootstrapped and tested as usual. Ok
On Wed, Jan 14, 2015 at 8:14 PM, Segher Boessenkool
wrote:
> Some hooks return word_mode by default, which is incorrect for -m32
> -mpowerpc64. This patch creates a new function rs6000_abi_word_mode
> to implement these hooks, and does so.
>
> This fixes 163 testuite FAILs.
>
> [ David already OK
On 01/14/15 16:52, Vladimir Makarov wrote:
The problem of unexpected code generation is discussed on
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64110
The following patch introduces 2 new constraints '^' and '$' which
are analogous to '?' and '!' but disfavor given alternative when *the
It's irony that I spent non-trivial effort to make sure basic_regex
still works after imbuing. :) But now with this specification, the
implementation can be cleaner (e.g. _M_original_str is removed).
Bootstrapped and tested.
I'll make a 4.9 patch later.
Thanks!
--
Regards,
Tim Shen
commit b22
On 01/14/15 12:20, Robert Suchanek wrote:
Hi Vladimir,
An issue has been identified with LRA when running CPU2006 h264ref benchmark.
I'll try to describe what the issue is and a fix applied as it is very
difficult to reproduce it and it is next to impossible to create a narrowed
testcase on top
On 01/14/15 08:19, Segher Boessenkool wrote:
"
@findex clobber
@item (clobber @var{x})
Represents the storing or possible storing of an unpredictable,
undescribed value into @var{x}, which must be a @code{reg},
@code{scratch}, @code{parallel} or @code{mem} expression.
[...]
If @var{x} is @code
On 07/01/14 15:34, Daniel Gutson wrote:
On Tue, Jul 1, 2014 at 2:25 PM, Jeff Law wrote:
On 03/19/14 08:06, Marcos Díaz wrote:
Well, finally I have the assignment, could you please review this patch?
Thanks.
My first thought was that if we've marked the function with an explicit
static prot
On Wed, Jan 14, 2015 at 8:53 PM, Tim Shen wrote:
> I'll make a 4.9 patch later.
Here it is. :)
Bootstrapped and tested.
--
Regards,
Tim Shen
commit 978246f3fb976d466d5735b43e416b77b750cd0d
Author: timshen
Date: Wed Jan 14 01:35:22 2015 -0800
PR libstdc++/64584
PR libstdc++
On January 15, 2015 6:06:33 AM CET, Jeff Law wrote:
>On 01/14/15 08:19, Segher Boessenkool wrote:
>
>> "
>> @findex clobber
>> @item (clobber @var{x})
>> Represents the storing or possible storing of an unpredictable,
>> undescribed value into @var{x}, which must be a @code{reg},
>> @code{scratch}
On 11/05/14 13:30, jb...@gmx.de wrote:
"Jeff Law" :
On 10/23/14 08:30, jb...@gmx.de wrote:
"Jeff Law" :
On 10/21/14 12:21, jb...@gmx.de wrote:
"Jeff Law" :
On 10/21/14 16:13, Haswell wrote:
The additional source must have the same requirement crossmodule-indircall-1.c
has.
* cros
On 11/05/14 13:30, jb...@gmx.de wrote:
With LTO enabled it runs just fine (which is the reason for the patch I
suggested):
This is definitely a testing framework problem. The profopt framework
isn't clearing the "additional_whatever" variables. Presumably failure
to clear is specific to a t
On 15.01.2015 00:52, Ian Lance Taylor wrote:
> On Wed, Jan 14, 2015 at 12:28 PM, Patrick Wollgast
> wrote:
>> On 14.01.2015 20:00, Ian Lance Taylor wrote:
>>> On Thu, Jan 8, 2015 at 12:33 PM, Patrick Wollgast
>>> wrote:
A short recap again:
Latest patch, changelog and a test progra
On 13/01/15 21:01, Andrew Stubbs wrote:
On 12/01/15 13:50, Ramana Radhakrishnan wrote:
In principle ok, but I'd like a comment in there explaining why we've
done this. Can you also post under what configurations these have been
tested ?
Is this better?
I tested it by running the vect.exp te
Moore, Catherine writes:
> > gcc/
> >
> > * config/mips/mips.h (MIPS_ISA_LEVEL_SPEC): Only infer an ISA
> > level from an ARCH; do not inject the default.
> > (MIPS_DEFAULT_ISA_LEVEL_SPEC): New macro split out from
> > MIPS_ISA_LEVEL_SPEC.
> > (MIPS_ISA_NAN2008_SPEC): Upda
> On 09 Jan 2015, at 00:42, Iain Sandoe wrote:
>
>
> On 8 Jan 2015, at 13:52, Tristan Gingold wrote:
>
>>
>>> On 08 Jan 2015, at 13:49, Iain Sandoe wrote:
>>>
>>> Hi Tristan,
>>>
>>> On 7 Jan 2015, at 10:15, Arnaud Charlet wrote:
>>>
Use _NSGetEnviron to get environment.
T
On Tue, Jan 13, 2015 at 5:35 PM, Aldy Hernandez wrote:
> Hi Richard.
>
> I'm chasing my tail here looking at an LTO + debug problem, and for the life
> of me I can't figure out how all this partition business affects a symbol's
> `analyzed' bit. Anyways... the documentation for all these function
On Tue, Jan 13, 2015 at 6:38 PM, Segher Boessenkool
wrote:
> On Tue, Jan 13, 2015 at 10:51:27AM +0100, Richard Biener wrote:
>> IMHO SHIFT_COUNT_TRUNCATED should be removed and instead
>> backends should provide shift patterns with a (and:QI ...) for the
>> shift amount which simply will omit that
On Wed, 14 Jan 2015, Prathamesh Kulkarni wrote:
> On 13 January 2015 at 22:02, Prathamesh Kulkarni
> wrote:
> > On 13 January 2015 at 16:06, Prathamesh Kulkarni
> > wrote:
> >> On 13 January 2015 at 15:34, Richard Biener wrote:
> >>> On Sun, 11 Jan 2015, Prathamesh Kulkarni wrote:
> >>>
>
> I think I got this right
>
>| Characteristics
>
> Target | HMSLQNFICBD lqrcpfgmbdiates
> ---+
> moxie | F g ds
Thanks, applied, but I think that 't' could be added because AFAICS every insn
(not expander) g
On Tue, Jan 13, 2015 at 11:47 PM, Andrew Pinski wrote:
> On Tue, Jan 13, 2015 at 2:41 PM, Rasmus Villemoes
> wrote:
>> [My first attempt at submitting a patch for gcc, so please forgive me
>> if I'm not following the right protocol.]
>
> There are a few things missing. For one, a testcase or tw
On 13/01/15 21:08, Andreas Tobler wrote:
> On 13.01.15 11:25, Ramana Radhakrishnan wrote:
>> On Thu, Jan 8, 2015 at 8:51 PM, Andreas Tobler
>> wrote:
>>> On 08.01.15 17:27, Richard Earnshaw wrote:
On 29/12/14 18:44, Andreas Tobler wrote:
>
> All,
>
> here is the third at
On 14 January 2015 at 07:35, Jeff Law wrote:
> On 01/13/15 11:55, Eric Botcazou wrote:
>>
>>
>>> (1) we have a non-paradoxical subreg;
>>> (2) both (reg:ymode xregno) and (reg:xmode xregno) occupy full
>>> hard registers (no padding or unused upper bits);
>>> (3) (reg:ymode xregno) and (reg:x
On 14/01/15 04:59, Hurugalawadi, Naveen wrote:
> Hi,
>
> Please find attached the patch that fixes abitest for ilp32.
>
> "testfunc_ptr" is a 32bit pointer in ILP32 but is being loaded as 64bit.
>
> Hence some of the func-ret testcases FAIL's for ILP32.
>
> Please review the patch and let us kn
On Mon, Jan 12, 2015 at 2:29 PM, Kyrill Tkachov wrote:
> Now with patch attached
>
> Kyrill
>
>
> On 12/01/15 14:27, Kyrill Tkachov wrote:
>>
>> Hi all,
>>
>> In this PR we ICE when compiling with -mtune=xscale. The ICE is a
>> segfault in xscale_sched_adjust_cost.
>> The root cause is that xscale
Hi there,
According to the latest EABI at
http://infocenter.arm.com/help/topic/com.arm.doc.ihi0045d/IHI0045D_ABI_adden
da.pdf, the new definition of Tag_ABI_HardFP_use is as below:
Tag_ABI_HardFP_use, (=27), uleb128
0 The user intended that FP use should be implied by Tag_FP_arch
1 The user inten
Hi, all,
In this patch of nds32 port:
https://gcc.gnu.org/ml/gcc-patches/2015-01/msg00799.html
Since we have a new option -mcmodel= as substitution for -mgp-direct,
we need to update documentation about such change accordingly.
The patch is attached and the plaintext ChangeLog is as follow.
gc
Hi, all,
In this patch of nds32 port:
https://gcc.gnu.org/ml/gcc-patches/2015-01/msg00969.html
Since we remove the implementation of -mforce-fp-as-gp, -mforbid-fp-as-gp,
and -mex9 options, we need to update documentation as well.
The patch is attached and the plaintext ChangeLog is as follow.
Hi All,
Here is updated patch which was redesigned accordingly to Richard review.
It performs swapping operands of commutative operations to expand the
expensive one first.
Bootstrap and regression testing did not show any new failures.
Is it OK for trunk?
gcc/ChangeLog
2015-01-14 Yuri Rumyant
Hi,
This patch is tuned particularly for benchmark performance on cortex-m7.
Tested with GCC regression test, no regressions. Is it ok for trunk?
BR,
Hale Wang
gcc/ChangeLog
2014-12-24 Hale Wang
* config/arm/arm.c: Tune the max_cond_insns/branch_cost for
Cortex-M7.
diff --gi
On 14/01/15 09:54, Terry Guo wrote:
> Hi there,
>
> According to the latest EABI at
> http://infocenter.arm.com/help/topic/com.arm.doc.ihi0045d/IHI0045D_ABI_adden
> da.pdf, the new definition of Tag_ABI_HardFP_use is as below:
>
> Tag_ABI_HardFP_use, (=27), uleb128
> 0 The user intended that FP u
On 14/01/15 10:14, Hale Wang wrote:
Hi,
This patch is tuned particularly for benchmark performance on cortex-m7.
Tested with GCC regression test, no regressions. Is it ok for trunk?
BR,
Hale Wang
gcc/ChangeLog
2014-12-24 Hale Wang
* config/arm/arm.c: Tune the max_cond_insns/branc
When compiling for size, live high registers are not saved in function prolog
in ARM backend in Thumb mode. The problem comes from
arm_conditional_register_usage setting call_used_regs for all high register to
avoid them being allocated. However, this cause prolog to not save these
register eve
On Wed, Jan 14, 2015 at 01:12:20PM +0300, Yuri Rumyantsev wrote:
> Hi All,
>
> Here is updated patch which was redesigned accordingly to Richard review.
> It performs swapping operands of commutative operations to expand the
> expensive one first.
>
> Bootstrap and regression testing did not show
Sorry, I resend correct patch.
Yuri.
2015-01-14 13:23 GMT+03:00 Jakub Jelinek :
> On Wed, Jan 14, 2015 at 01:12:20PM +0300, Yuri Rumyantsev wrote:
>> Hi All,
>>
>> Here is updated patch which was redesigned accordingly to Richard review.
>> It performs swapping operands of commutative operations
Hi all,
-mapcs-frame (and its' alias -mapcs) are somewhat bitrotten and the ABI
they represent is deprecated anyway so this is a patch to deprecate the
option. It's not being removed here, just documented as deprecated.
Kyrill
2015-01-14 Kyrylo Tkachov
* doc/invoke.texi (mapcs): Ment
Hi all,
I'm proposing a gas patch to add warnings for deprecated forms of ldm in
ARMv7-A.
(https://sourceware.org/ml/binutils/2015-01/msg00158.html)
Unfortunately, GCC generates these deprecated forms with -mapcs-frame.
Since the deprecation happens only from armv7-a onwards, this patch adds
-
Hi all,
This is a wwwdocs patch to changes.html to announce the deprecation of
the -mapcs and -mapcs-frame options.
Ok to apply if we decide to deprecate it?
Thanks,
KyrillIndex: htdocs/gcc-5/changes.html
===
RCS file: /cvs/gcc/w
Hi all,
In the arm version of arm_neon.h we error out early if the user tries to
use that header without NEON.
In aarch64 AdvancedSIMD is available by default unless the user
explicitly disables it.
Still it would be more helpful if we could just error out gracefully
instead of dumping a long
On Wed, Jan 14, 2015 at 01:32:13PM +0300, Yuri Rumyantsev wrote:
> Sorry, I resend correct patch.
> +reorder_operands (basic_block bb)
> +{
> + unsigned int *lattice; /* Hold cost of each statement. */
> + unsigned int i = 0, n = 0;
> + gimple_stmt_iterator gsi;
> + gimple_seq stmts;
> + gi
Hello,
Test case g++.dg/torture/20141013.C (added
https://gcc.gnu.org/ml/gcc-patches/2014-10/msg01190.html) triggers the
warning
--
20141013.C:45:23: warning: width of 'tree_base::code' exceeds its type
--
on arm-none-eabi.
The code specifies a bitfield of size 16 with an enum as the underl
The following fixes PR59354 by treating loads from a group larger
than the SLP size as having gaps if the loop is unrolled. This
usually means we combine parts of the group of different unroll
interations which effectively introduces a gap.
Of course in the end this check should be postponed and
Hello.
Following patch introduces target option support for array types. As discussed
in
[1], the patch is tested on a nios2 target machine.
Ready for trunk?
Thanks,
Martin
[1] https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64377
>From 8f32501a6ea3989a44b76fc3ead2f70d1b636b7a Mon Sep 17 00:00:00
On Wed, Jan 14, 2015 at 11:45 AM, Jakub Jelinek
wrote:
> On Wed, Jan 14, 2015 at 01:32:13PM +0300, Yuri Rumyantsev wrote:
>> Sorry, I resend correct patch.
>
>> +reorder_operands (basic_block bb)
>> +{
>> + unsigned int *lattice; /* Hold cost of each statement. */
>> + unsigned int i = 0, n =
On Wed, Jan 14, 2015 at 11:58:50AM +0100, Richard Biener wrote:
> >> + /* Swap operands if the second one is more expensive. */
> >> + def0 = get_gimple_for_ssa_name (op0);
> >> + if (!def0)
> >> + continue;
> >> + def1 = get_gimple_for_ssa_name (op1);
> >> + if (!def1
On 14/01/15 10:38, Kyrill Tkachov wrote:
> Hi all,
>
> -mapcs-frame (and its' alias -mapcs) are somewhat bitrotten and the ABI
> they represent is deprecated anyway so this is a patch to deprecate the
> option. It's not being removed here, just documented as deprecated.
>
> Kyrill
>
> 2015-01-
On 14/01/15 11:13, Richard Earnshaw wrote:
On 14/01/15 10:38, Kyrill Tkachov wrote:
Hi all,
-mapcs-frame (and its' alias -mapcs) are somewhat bitrotten and the ABI
they represent is deprecated anyway so this is a patch to deprecate the
option. It's not being removed here, just documented as de
1 - 100 of 176 matches
Mail list logo
