>>> On 17.07.15 at 06:26, wrote:
> Which imported packages use configure.in? I'm happy to submit patches
> for those, too.
The answer to this may not even matter - consuming components
(like gcc is in respect to binutils) shouldn't assume only the newer
name is used: It should remain to be possi
Hello!
When moving precompute_register_parameters, I didn't notice that the
call was wrapped with NO_DEFER_POP/OK_DEFER_POP.
Attached patch fixes this oversight.
2015-07-17 Uros Bizjak
PR rtl-optimization/66891
* calls.c (expand_call): Wrap precompute_register_parameters with
NO_
Hi,
This patch is to fix PR66388. It's an old issue but recently became worse
after my scev overflow change. IVOPT now can only compute iv use with
candidate which has at least same type precision. See below code:
if (TYPE_PRECISION (utype) > TYPE_PRECISION (ctype))
{
/* We do not h
On 07/17/2015 12:35 AM, Sebastian Pop wrote:
gcc/ChangeLog:
2015-07-16 Aditya Kumar
Sebastian Pop
* common.opt (floop-fuse): New.
* doc/invoke.texi (floop-fuse): Documented.
* graphite-optimize-isl.c (optimize_isl): Use
ISL_SCHEDULE_FUSE
On 07/17/2015 12:23 AM, Sebastian Pop wrote:
This fixes bootstrap of GCC with BOOT_CFLAGS="-g -O2 -fgraphite-identity
-floop-nest-optimize -floop-block -floop-interchange -floop-strip-mine".
It passes regstrap on amd64-linux.
Ok to commit to trunk?
Very nice.
this but seems to include multip
> Since all configure files are generated from them, this patch must be
> checked in first.
> But some of them are imported and some imported packages still use
> configure.in,
> not configure.ac.
>
> What is the real value of changing "configure.in" in comments/messages to
> "configure.ac" when b
On Thu, Jul 16, 2015 at 8:09 PM, Michael Darling wrote:
> (I was requested by binutils to split my May 24 and Jul 16 patches
> into separate files for each binutils-gdb main subdirectory.)
>
> Combined builds has been broken for about 10 months, because some binutils
> configure.in files were rena
On 07/16/2015 09:21 AM, Kyrill Tkachov wrote:
Hi all,
This patch adds the documentation for the AArch64 target attributes and
pragmas.
Ok for trunk?
The content looks OK, but I have a bunch of nit-picky comments about
grammar, typos, markup, etc
+The following target-specific function
(I was requested by binutils to split my May 24 and Jul 16 patches
into separate files for each binutils-gdb main subdirectory.)
Combined builds has been broken for about 10 months, because some binutils
configure.in files were renamed to configure.ac, but gcc's references to them
were not updated
(I was requested by binutils to split my May 24 and Jul 16 patches
into separate files for each binutils-gdb main subdirectory.)
Combined builds has been broken for about 10 months, because some binutils
configure.in files were renamed to configure.ac, but gcc's references to them
were not updated
(I was requested by binutils to split my May 24 and Jul 16 patches
into separate files for each binutils-gdb main subdirectory.)
Combined builds has been broken for about 10 months, because some binutils
configure.in files were renamed to configure.ac, but gcc's references to them
were not updated
(I was requested by binutils to split my May 24 and Jul 16 patches
into separate files for each binutils-gdb main subdirectory.)
Combined builds has been broken for about 10 months, because some binutils
configure.in files were renamed to configure.ac, but gcc's references to them
were not updated
(I was requested by binutils to split my May 24 and Jul 16 patches
into separate files for each binutils-gdb main subdirectory.)
Combined builds has been broken for about 10 months, because some binutils
configure.in files were renamed to configure.ac, but gcc's references to them
were not updated
(I was requested by binutils to split my May 24 and Jul 16 patches
into separate files for each binutils-gdb main subdirectory.)
Combined builds has been broken for about 10 months, because some binutils
configure.in files were renamed to configure.ac, but gcc's references to them
were not updated
(I was requested by binutils to split my May 24 and Jul 16 patches
into separate files for each binutils-gdb main subdirectory.)
Combined builds has been broken for about 10 months, because some binutils
configure.in files were renamed to configure.ac, but gcc's references to them
were not updated
(I was requested by binutils to split my May 24 and Jul 16 patches
into separate files for each binutils-gdb main subdirectory.)
Combined builds has been broken for about 10 months, because some binutils
configure.in files were renamed to configure.ac, but gcc's references to them
were not updated
(I was requested by binutils to split my May 24 and Jul 16 patches
into separate files for each binutils-gdb main subdirectory.)
Combined builds has been broken for about 10 months, because some binutils
configure.in files were renamed to configure.ac, but gcc's references to them
were not updated
(I was requested by binutils to split my May 24 and Jul 16 patches
into separate files for each binutils-gdb main subdirectory.)
Combined builds has been broken for about 10 months, because some binutils
configure.in files were renamed to configure.ac, but gcc's references to them
were not updated
(I was requested by binutils to split my May 24 and Jul 16 patches
into separate files for each binutils-gdb main subdirectory.)
Combined builds has been broken for about 10 months, because some binutils
configure.in files were renamed to configure.ac, but gcc's references to them
were not updated
(I was requested by binutils to split my May 24 and Jul 16 patches
into separate files for each binutils-gdb main subdirectory.)
Combined builds has been broken for about 10 months, because some binutils
configure.in files were renamed to configure.ac, but gcc's references to them
were not updated
(I was requested by binutils to split my May 24 and Jul 16 patches
into separate files for each binutils-gdb main subdirectory.)
Combined builds has been broken for about 10 months, because some binutils
configure.in files were renamed to configure.ac, but gcc's references to them
were not updated
(I was requested by binutils to split my May 24 and Jul 16 patches
into separate files for each binutils-gdb main subdirectory.)
Combined builds has been broken for about 10 months, because some binutils
configure.in files were renamed to configure.ac, but gcc's references to them
were not updated
The following:
#pragma omp ordered depend(sink:asdf)
...where asdf is undeclared, is ICEing in *finish_omp_clauses because we
create a clause with NULL, and we're expecting a TREE_LIST.
In the attached patch, I have opted to avoid creating the ordered depend
clause if we have a parse error.
Ping. I don't have write access.
The attached patch still works with current trunk source, only failing
on the ChangeLog due to submissions since then.
On Fri, Jul 3, 2015 at 9:50 PM, Michael Darling wrote:
> The addition of libstdc++fs broke an inexact and fragile method in the
> libstdc++-v3/
> 2015-07-16 Steven G. Kargl
>
> * io.c (is_char_type): Call gfc_resolve_expr().
> (match_open_element, match_dt_element, match_inquire_element): Fix
> ASYNCHRONOUS case.
OK to commit
gcc/ChangeLog:
2015-07-16 Aditya Kumar
Sebastian Pop
* common.opt (floop-fuse): New.
* doc/invoke.texi (floop-fuse): Documented.
* graphite-optimize-isl.c (optimize_isl): Use
ISL_SCHEDULE_FUSE_MAX when using flag_loop_fuse.
* graphite-p
This fixes bootstrap of GCC with BOOT_CFLAGS="-g -O2 -fgraphite-identity
-floop-nest-optimize -floop-block -floop-interchange -floop-strip-mine".
It passes regstrap on amd64-linux.
Ok to commit to trunk?
Thanks.
2015-07-15 Aditya Kumar
Sebastian Pop
PR middle-end/61929
On Fri, Jul 10, 2015 at 06:35:30PM +0200, Mikael Morin wrote:
> Ping: https://gcc.gnu.org/ml/fortran/2015-06/msg00075.html
>
Patch looks ok to me.
--
Steve
See any dictionary for the definition of 'old'. :-)
Last time I used VMS in 1990i, and upgrading to
newer versions of software on the systems required
a few hurdles to clear.
On Thu, Jul 16, 2015 at 02:13:54PM -0700, Douglas B Rupp wrote:
> VMS hasn't had a 3 character filename extension limit
On Jul 16, 2015, Richard Biener wrote:
>> Is this ok to install?
> Yes.
So, I decided to run a ppc64le-linux-gnu bootstrap, just in case, and
there are issues with split complex parms that caused go and fortran
libs to fail the build.
I will refrain from installing this for now, and I'll post
VMS hasn't had a 3 character filename extension limit since before
VAX/VMS version 4.0 was released in 1984.
On 07/16/2015 01:41 PM, Steve Kargl wrote:
On Thu, Jul 16, 2015 at 05:08:50PM +0200, Paul Richard Thomas wrote:
Please find attached a new version of the patch that fixes the
inconsist
On Thu, Jul 16, 2015 at 05:08:50PM +0200, Paul Richard Thomas wrote:
>
> Please find attached a new version of the patch that fixes the
> inconsistency with the standard, pointed out by Reinhold. It is weird
> but a read the appropriate part of the standard several times and
> simply did not pick
Jakub, Ilya,
this patch against trunk constifies the offload target data. I'm having
difficulty building an intelmic toolchain, so the changes there aren't tested.
Ilya, if you could check them, that'd be great.
nathan
2015-07-16 Nathan Sidwell
gcc/
* config/nvptx/mkoffload.c (process):
The attached patch is needed to fully address PR fortran/66724 and
fortran/66725. In is_char_type(), we need to call gfc_resolve_expr
to properly resolve the tag, e.g., ASYNCHRONOUS="Y"//"E"//"S".
At the same time, I forgot call is_char_type for ASYNCHRONOUS.
Regression tested on trunk. OK to com
Committed to trunk as r225905.
gcc/jit/ChangeLog:
* docs/internals/index.rst (Overview of code structure): Add note
that the implementation is in C++, despite the .c extension.
(Submitting patches): New subsection.
* docs/_build/texinfo/libgccjit.texi: Regenerate.
-
On 07/16/2015 07:54 AM, Andrew MacLeod wrote:
On 07/16/2015 03:27 AM, Richard Biener wrote:
On Wed, 15 Jul 2015, Andrew MacLeod wrote:
admittedly neither situation is very common I suspect, but it does
seem like a
hidden gotchya waiting to happen.
I guess we either want to checking-assert th
On 16/07/15 19:28, Segher Boessenkool wrote:
On Thu, Jul 16, 2015 at 07:17:54PM +0100, Kyrill Tkachov wrote:
If you always want to simplify first, does it work to move this whole big
block behind the simplify just following it? Or do you want to simplify
after the transform as well?
You mean
On Thu, Jul 16, 2015 at 07:17:54PM +0100, Kyrill Tkachov wrote:
> >If you always want to simplify first, does it work to move this whole big
> >block behind the simplify just following it? Or do you want to simplify
> >after the transform as well?
>
> You mean move this hunk outside the "if (BINA
"Jan Beulich" writes:
> 2015-07-16 Jan Beulich
>
> * config/t-softfp: Split up "else ifneq".
This is OK.
Thanks.
Ian
On 16/07/15 19:13, Segher Boessenkool wrote:
On Thu, Jul 16, 2015 at 04:25:14PM +0100, Kyrill Tkachov wrote:
Hi all,
This is an attempt to solve the problem in the thread starting at
https://gcc.gnu.org/ml/gcc-patches/2015-07/msg01010.html
in a generic way after some pointers from Segher and A
On Thu, Jul 16, 2015 at 04:25:14PM +0100, Kyrill Tkachov wrote:
> Hi all,
>
> This is an attempt to solve the problem in the thread starting at
> https://gcc.gnu.org/ml/gcc-patches/2015-07/msg01010.html
> in a generic way after some pointers from Segher and Andrew.
>
> The problem I got was that
On 07/13/15 10:33, Bernd Schmidt wrote:
On 07/13/2015 03:57 PM, Nathan Sidwell wrote:
this patch changes the offload target data type from an array of void *,
to a struct, which is somewhat easier to deal with than remembering
numeric indices and type casts.
This is step 1 in reworking the lau
On 07/16/15 11:32, Julian Brown wrote:
Hi,
This patch removes the device-specific filtering (for NVidia PTX) from
the parsing stages of the host compiler (for the device_type clause --
separately for C, C++ and Fortran) in favour of fully parsing the
device_type clauses, but not actually impleme
I've committed this patch to fix a bug in the worker spill/fill code. We ended
up not incrementing the pointer, resulting in the stack frame being filled with
the same value.
Thanks to Jim for finding the failure.
nathan
2015-07-16 Nathan Sidwell
* config/nvptx/nvptx.c (nvptx_gen_wcast):
Hi!
This patch adds support for 4 new combined constructs and fixes various
issues in the clause splitting code and other issues I found on the
new testcases.
2015-07-16 Jakub Jelinek
gcc/
* omp-low.c (expand_omp_build_assign): Add prototype. Add AFTER
argument, if true emit
Sorry, had sent out the wrong version.
This is the right patch.
Thanks,
Kyrill
On 16/07/15 16:20, Kyrill Tkachov wrote:
Hi all,
This patch transforms the Cortex-A53 erratum 835769 workaround checks into a
macro.
This way we don't have to override aarch64_fix_a53_err835769 in the default case
Hi all,
This patch improves codegen for expressions of the form:
(x ? y + c1 : y + c2) when |c1 - c2| == 1
It matches the if_then_else of the two plus-immediates,
performs one of them, then generates a conditional increment
operation.
Thus, for the code in the testcase we generate a single add,
Hi,
This patch removes the device-specific filtering (for NVidia PTX) from
the parsing stages of the host compiler (for the device_type clause --
separately for C, C++ and Fortran) in favour of fully parsing the
device_type clauses, but not actually implementing anything for them
(device_type supp
Hi all,
This scan-assembler test was failing for me when testing with an explicit
/-march=armv7-a variant because
it clashed with the -mcpu=cortex-m7 and overrode it.
This patch skips the test if the user forces an incompatible -march or -mcpu
option.
The test now appears as UNSUPPORTED in the
Hi all,
In this second patch I add the transformation mentioned in the subject to
simplify-rtx.c.
In combination with the first patch to combine, combine_simplify_rtx now picks
it up in the
testcase and does the right thing by not emitting an extra negate after the
conditional negate
operation
Hi all,
This is an attempt to solve the problem in the thread starting at
https://gcc.gnu.org/ml/gcc-patches/2015-07/msg01010.html
in a generic way after some pointers from Segher and Andrew.
The problem I got was that combine_simplify_rtx was trying to
do some special handling of unary operatio
The following patch fixes PR66626
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66626
The previous patch solved only one problem (the 2nd test case in the
PR). The following patch solves the all test cases.
The patch was tested and bootstrapped on x86/x86-64.
Committed as rev. 225891
Hi all,
This patch improves compilation times for code using the arm_neon.h intrinsics.
The problem there is that since we now wrap all the intrinsics in arm_neon.h
inside a pragma,
the midend will apply the pragma string onto every single intrinsic as an
attribute, calling
the target attribute
Hi all,
This patch adds the documentation for the AArch64 target attributes and pragmas.
Ok for trunk?
Thanks,
Kyrill
2015-07-16 Kyrylo Tkachov
* doc/extend.texi (AArch64 Function Attributes): New node.
(AArch64 Pragmas): Likewise.
commit 533fdcf9675b1364d0bf8446601b2509d9987e3a
Au
Hi all,
This patch fixes an ICE that I encountered while testing the series.
The testcase in the patch ICEs during builtin expansion because the testcase
is compiled with +nofp which means the builtin SIMD types are laid out
according to the nofp rules, but later when a function tagged with +simd
Hi all,
These are the tests for target attributes and pragmas.
I've tried to test for the inlining rules, some of the possible errors and the
preprocessor macros changed from target pragmas.
Ok for trunk?
Thanks,
Kyrill
2015-07-16 Kyrylo Tkachov
* gcc.target/aarch64/pragma-cpp-predefs
Hi all,
This patch implements target pragmas for aarch64.
The pragmas accepted are the same as for target attributes (as required).
In addition pragmas will need to redefine the target-specific preprocessor
macros if appropriate.
A new file: aarch64-c.c is added and the code from TARGET_CPU_CPP_
Hi all,
This patch implements target attribute support via the
TARGET_OPTION_VALID_ATTRIBUTE_P hook.
The aarch64_handle_option function in common/config/aarch64/aarch64-common.c is
exported to the
backend and beefed up a bit.
The target attributes supported by this patch reflect the command-li
Hi all,
This patch implements TARGET_SET_CURRENT_FUNCTION and defines SWITCHABLE_TARGET.
With this patch in the series, we should be far enough to get LTO option
switching to work properly.
The implementation if TARGET_SET_CURRENT_FUNCTION is pretty much a direct copy
from the rs6000 backend,
Hi all,
This patch implements the target-specific inlining rules.
The basic philosophy is that we want to definitely reject inlining if the
callee's architecture
is not a subset, feature-wise, of the caller's.
Beyond that, we want to allow inlining if the callee is always_inline.
If it's not, w
Hi all,
This one is more meaty than the previous ones. It buffs up the parsing
functions for
the mcpu, march, mtune options, decouples them and makes them return an enum
describing
the errors that may occur. This will allow us to use these functions in other
contexts
beyond aarch64_override_o
Hi all,
This is one of the main patches in the series.
The backend compilation state can be described by the options in aarch64.opt
marked as Save.
This causes the options-save.c machinery to save and restore them when asked
them and the
TARGET_OPTION_SAVE and TARGET_OPTION_RESTORE should handl
Hi all,
This patch transforms the Cortex-A53 erratum 835769 workaround checks into a
macro.
This way we don't have to override aarch64_fix_a53_err835769 in the default case
and this allows us to keep track of when the user doesn't specify this option,
which may come in handy later on when we dec
Hi all,
This patch wraps aarch64_frame_pointer_required into a
TARGET_OMIT_LEAF_FRAME_POINTER macro
and initializes aarch64_frame_pointer_required to 2 instead of 1, allowing us
to detect from
aarch64_frame_pointer_required whether the user explicitly specified
-momit-leaf-frame-pointer
or -mn
Hi all,
In this second patch I want to get to the point where I can get an enum that I
can use
to index all_architectures to get the current architecture being used, similar
to what we
do in patch 1/N.
The closest thing to what I want in aarch64-arches.def is the 3rd field which
specifies the
Hi all,
This first patch adds a field to the processor structure that uniquely
identifies that processor.
Note that the current 'core' field is actually just the core for which to
schedule the instructions.
With this patch we get the nice property that we can reference a processor
struct by ju
Hi all,
This series implements the hooks required to enable SWITCHABLE_TARGET for the
aarch64 port.
This series allows the aarch64 compiler to sanely handle LTO compilation of
files compiled
with different target-specific options.
The first 5 patches refactor the option handling machinery and
Dear Reinhold, dear all,
Please find attached a new version of the patch that fixes the
inconsistency with the standard, pointed out by Reinhold. It is weird
but a read the appropriate part of the standard several times and
simply did not pick up the critical information :-)
Note that the delimit
On Thu, Jul 16, 2015 at 07:57:56AM -0700, Aldy Hernandez wrote:
> @@ -13828,6 +13828,14 @@ tsubst_omp_for_iterator (tree t, int i, tree declv,
> tree initv,
>
>init = TREE_VEC_ELT (OMP_FOR_INIT (t), i);
>gcc_assert (TREE_CODE (init) == MODIFY_EXPR);
> +
> + if (orig_declv && OMP_FOR_ORI
On 16/07/15 16:00, Michael Matz wrote:
> Hi,
>
> On Thu, 16 Jul 2015, Richard Earnshaw wrote:
>
> Now that we do have the problem, we can't fix it without an ARM port
> ABI change, which is undesirable, so we may have to fix it with a MI
> change.
What's the ABI implicatio
Hi,
On Thu, 16 Jul 2015, Richard Earnshaw wrote:
> >>> Now that we do have the problem, we can't fix it without an ARM port
> >>> ABI change, which is undesirable, so we may have to fix it with a MI
> >>> change.
> >>
> >> What's the ABI implication of fixing the inconsistency?
> >
>
> I thin
On 07/16/2015 12:06 AM, Jakub Jelinek wrote:
Hi!
CCing Jason on a tsubst issue below.
On Wed, Jul 15, 2015 at 06:05:06PM -0700, Aldy Hernandez wrote:
As I said on IRC, this looks ugly, but I can see why you wouldn't want the
extra word on all loop variants. I've implemented it as requested.
Hi,
On Thu, 16 Jul 2015, Richard Biener wrote:
> > Similar, if the condition is an atom you should be able to leave the
> > parens away:
> >
> > (switch
> > cond (minus @0 @1)
> > )
> >
> > (given a predicate 'cond' defined appropriately).
>
> Yes. Though techincally the condition cannot
> On Jul 15, 2015, at 8:58 AM, Mikael Morin wrote:
>
> The patch itself looks good to me.
> A ChangeLog entry should be provided with it.
> The test is missing the usual dejagnu pattern matching directives to
> check the generated code.
> Do you have commit rights?
Hi Mikael,
Thanks for the q
Hi,
Another patch with a pipeline description but for M51xx cores with
two new options introduced: -march={m5100,m5101}. The M5101 is essentially
the same as M5100 but mapped to -msoft-float.
Ok to apply?
Regards,
Robert
2015-07-16 Prachi Godbole
gcc/
* config/mips/m5100.md: New fi
Hi,
This patch adds a pipeline description for the I6400 processor with -mips32r6
and -mips64r6 defaulted to this description.
Regtested with mips-img-linux-gnu. mips-tables.opt will be regenerated before
committing depending on which patch from the series goes in first.
Ok to apply?
Regards,
R
Hi,
As in the title, the attached patch adds -march=interaptiv defined to 24kf2_1,
mapped to -mips32r2 and -mdsp.
OK to apply?
Regards,
Robert
gcc/
* config/mips/mips-cpus.def (interaptiv): Define.
* config/mips/mips-tables.opt: Regenerate.
* config/mips/mips.h (MIPS_IS
The pattern was accepting a nonimediate_operand, using the C condition
to weed out certain types of memory, but was then using an "r" constraint
to force a register. This patch makes the predicate match the constraint
and removes the C condition.
Tested by building fr30-elf and using:
int
foo (i
On 07/09/2015 10:47 PM, Martin Liška wrote:
> On 07/09/2015 07:44 PM, Jeff Law wrote:
>> On 07/09/2015 03:13 AM, mliska wrote:
>>> gcc/ChangeLog:
>>>
>>> 2015-07-03 Martin Liska
>>>
>>> * ipa-pure-const.c (struct funct_state_d): New.
>>> (funct_state_d::default_p): Likewise.
>>> (has
On 07/10/2015 03:30 PM, Martin Jambor wrote:
> Hi,
>
> I've spotted a likely typo:
>
> On Thu, Jul 09, 2015 at 11:13:53AM +0200, Martin Liska wrote:
>> gcc/ChangeLog:
>>
>> 2015-07-03 Martin Liska
>>
>> * ipa-reference.c (ipa_ref_opt_summary_t): New class.
>> (get_reference_optimizat
On Thu, Jul 16, 2015 at 3:39 PM, Martin Liška wrote:
> Hello.
>
> Following patch fixes $subject, which can be spotted on gcc-5-branch, while
> trunk
> looks fine (even though it can potentially suffer from the same issues).
>
> Patch can both survive regression tests on trunk and gcc-5-branch on
On 07/10/2015 04:18 PM, Martin Jambor wrote:
> Hi,
>
> I know the patch has been approved by Jeff, but please do not commit
> it before considering the following:
>
> On Thu, Jul 09, 2015 at 11:13:53AM +0200, Martin Liska wrote:
>> gcc/ChangeLog:
>>
>> 2015-07-03 Martin Liska
>>
>> * ipa-
On 07/10/2015 03:31 PM, Martin Jambor wrote:
> Hi,
>
> thanks for working on this and sorry for a tad late review:
>
> On Thu, Jul 09, 2015 at 11:13:52AM +0200, Martin Liska wrote:
>> gcc/ChangeLog:
>>
>> 2015-07-03 Martin Liska
>>
>> * cgraph.c (symbol_table::create_edge): Introduce summ
This patch gets read_md_rtx to return a structure that describes the rtx rather
than separate fields. This includes the location of the start of the rtx as
a file_location. A follow-on patch will use this to remove define_split and
define_peephole2 from the insn_code numbering.
This removes the
Another patch to make more use of fatal_at (which passes a file location)
rather than fatal (which gives no indication where the error was).
Series bootstrapped & regression-tested on x86_64-linux-gnu. I built gcc
before and after the series for one target per CPU directory and checked
that the o
Make genpreds.c use a file_location rather than a plain lineno. This means
that it will cope with changes in filename, e.g. when reporting contradictions
between two define_constraints.
Series bootstrapped & regression-tested on x86_64-linux-gnu. I built gcc
before and after the series for one t
Make up to 3.80 (documented as minimal permitted version) doesn't
support "else if...".
2015-07-16 Jan Beulich
* config/t-softfp: Split up "else ifneq".
--- a/libgcc/config/t-softfp
+++ b/libgcc/config/t-softfp
@@ -103,7 +103,8 @@ ifeq ($(enable_shared),yes)
fi
endif
Use file_location to replace separate filename and line number
in genoutput.c.
Series bootstrapped & regression-tested on x86_64-linux-gnu. I built gcc
before and after the series for one target per CPU directory and checked
that the output was the same (except for some filename fixes later in
th
This includes replacing calls to fatal() (without a file location)
with calls to a new function fatal_at, which should improve error
reporting.
Series bootstrapped & regression-tested on x86_64-linux-gnu. I built gcc
before and after the series for one target per CPU directory and checked
that th
Add a file_location type for recoding the position in an .md file. Also
add error_at and message_at functions for reporting diagnostics against
a particular position.
read_skip_construct is local to read-md.c so I removed its prototype rather
than update it.
Series bootstrapped & regression-test
Hello.
Following patch fixes $subject, which can be spotted on gcc-5-branch, while
trunk
looks fine (even though it can potentially suffer from the same issues).
Patch can both survive regression tests on trunk and gcc-5-branch on
x86_64-linux-pc.
Ready for both branches?
Thanks,
Martin
>From
genoutput.c:next_index_number is only used to set a structure field that
itself is never used. I think this dates from before the recent fad for
including filenames and line numbers in error messages.
Series bootstrapped & regression-tested on x86_64-linux-gnu. I built gcc
before and after the s
check_attr_value and make_canonical have some checks for null attr arguments,
but all callers would segfault if the argument really were null.
This is preparing for some improvements to the source location tracking
in gen*.
Series bBootstrapped & regression-tested on x86_64-linux-gnu. I built gc
3 patterns related to setjmp/longjmp/non-local gotos call adjust_address_nv
and this can break (generate unrecognizable insns) when things get serious,
for example if you configure with --enable-sjlj-exceptions.
Tested on SPARC/Solaris, applied on the mainline.
2015-07-16 Eric Botcazou
On 07/16/15 07:41, Ilya Verbin wrote:
On Wed, Jul 15, 2015 at 20:56:50 -0400, Nathan Sidwell wrote:
Index: gcc/config/nvptx/mkoffload.c
===
- fprintf (out, "extern void *__OFFLOAD_TABLE__[];\n\n");
+ fprintf (out, "extern const vo
On 07/16/2015 03:27 AM, Richard Biener wrote:
On Wed, 15 Jul 2015, Andrew MacLeod wrote:
admittedly neither situation is very common I suspect, but it does seem like a
hidden gotchya waiting to happen.
I guess we either want to checking-assert that we never hit that
special marker or handle it
On Wed, Jul 15, 2015 at 20:56:50 -0400, Nathan Sidwell wrote:
> Index: gcc/config/nvptx/mkoffload.c
> ===
> - fprintf (out, "extern void *__OFFLOAD_TABLE__[];\n\n");
> + fprintf (out, "extern const void *conat __OFFLOAD_TABLE__[];\n\
Bootstrapped and tested on x86_64-unknown-linux-gnu, applied.
Richard.
2015-07-16 Richard Biener
PR tree-optimization/66894
* tree-vrp.c (register_edge_assert_for_2): Fix bad assumption
about deriving NE_EXPR from truncated values.
* gcc.dg/torture/pr66894.c:
On 16/07/15 12:23, Richard Biener wrote:
On Thu, Jul 16, 2015 at 12:19 PM, Thomas Schwinge
wrote:
Hi Tom!
On Thu, 16 Jul 2015 10:46:00 +0200, Richard Biener
wrote:
On Wed, Jul 15, 2015 at 10:26 PM, Tom de Vries wrote:
I tried to parallelize this fortran test-case (based on autopar/outer-1
On 07/09/2015 06:24 PM, Jeff Law wrote:
> On 07/09/2015 07:56 AM, mliska wrote:
>> gcc/ChangeLog:
>>
>> 2015-07-09 Martin Liska
>>
>> * dbgcnt.def: Add new debug counter.
>> * ipa-icf-gimple.c (func_checker::compare_ssa_name): Add flag
>> for strict mode.
>> (func_checker::compar
1 - 100 of 143 matches
Mail list logo
