Dear Steve,
This is also OK to commit.
Thanks
Paul
On 24 October 2015 at 01:52, Steve Kargl
wrote:
> The attached patch has been built and tested on x86_64-*-freebsd.
> It implements a check for validate kinds in type declarations
> of the form REAL*42.
>
> OK to commit?
>
> 2015-10-23 Steven
Dear Steve,
This is OK to commit.
Thanks for the patch
Paul
On 23 October 2015 at 21:29, Steve Kargl
wrote:
> On Fri, Oct 23, 2015 at 12:28:14PM -0700, Steve Kargl wrote:
>> Built and regression tested on x86_64-*-freebsd.
>> OK to commit?
>>
>
> Now with the patch attached!
>
> --
> Steve
On 10/21/2015 12:16 AM, Richard Biener wrote:
On Tue, Oct 20, 2015 at 9:10 PM, Jason Merrill wrote:
I made this change on the delayed folding branch and then noticed that it
broke pointer-arith-10.c, which you added to the testsuite. The patch
changes the -original dump from
return (char *
At the last C++ meeting in Lenexa, I observed that the resolution for DR
1630 resolved 1518 by saying that default-initialization could call an
explicit default constructor. Since then there was wide sentiment from
the library working group that this was a wrong resolution, so at this
meeting
On 10/23/2015 01:29 PM, Cesar Philippidis wrote:
> On 10/22/2015 08:00 AM, Jakub Jelinek wrote:
>> On Thu, Oct 22, 2015 at 07:47:01AM -0700, Cesar Philippidis wrote:
But it is unclear from the parsing what from these is allowed:
>>>
>>> int v, w;
>>> ...
>>> gang(26) // equivalent to gang(num
On 10/23/2015 01:25 PM, Cesar Philippidis wrote:
> On 10/22/2015 01:52 AM, Jakub Jelinek wrote:
>> On Wed, Oct 21, 2015 at 03:18:55PM -0400, Nathan Sidwell wrote:
>>> This patch is the C++ changes matching the C ones of patch 4. In
>>> finish_omp_clauses, the gang, worker, & vector clauses are han
On 10/23/2015 02:31 PM, Cesar Philippidis wrote:
> On 10/23/2015 01:31 PM, Jakub Jelinek wrote:
>> On Fri, Oct 23, 2015 at 01:17:07PM -0700, Cesar Philippidis wrote:
>>> Good idea, thanks. This patch also corrects the problems parsing weird
>>> combinations of num, static and length arguments that
On 10/23/15 16:56, Richard Biener wrote:
> On Thu, Oct 22, 2015 at 9:46 PM, Jeff Law wrote:
>>
>> Note that the call to fold_binary from tree-ssa-sccvn.c has been removed.
>> So that hunk either needs to be removed or the change applied elsewhere.
>>
Oh, really, it uses gimple_simplify instead o
The attached patch has been built and tested on x86_64-*-freebsd.
It implements a check for validate kinds in type declarations
of the form REAL*42.
OK to commit?
2015-10-23 Steven G. Kargl
PR fortran/68055
* decl.c (gfc_match_decl_type_spec): Check for valid kind in old-style
Hi,
as discussed earlier, the types_compatible_p in operand_equal_p seems redundant.
(it is callers work to figure out how much of type matching it wants. If not,
we probably want to treat most of other references and casts simlar way).
Bootstrapped/regtested x86_64-linux. OK?
* fold-con
On Thu, 17 Sep 2015, Mark Wielaard wrote:
>>> I believe making -Wunused-const-variable part of -Wall is not
>>> a good idea.
>>>
>>> For example, I have a nightly build of Wine with a nightly build
>>> of GCC. And my notifaction mail went from twently lines of warning
>>> to 6500 -- all coming fro
cxa_atexit functionality for AIX was added to libgcc a while ago. It
seems stable in all of the testing. This patch enables it by default.
Bootstrapped on powerpc-ibm-aix7.1.0.0, powerpc-ibm-aix7.1.2.0,
powerpc-ibm-aix7.1.3.0
Thanks, David
* config.gcc (powerpc-ibm-aix[6789])[default_use_cxa_a
On 10/23/2015 04:22 PM, Caroline Tice wrote:
This patch fixes a compile-time regression that was originally
introduced by the fix
for PR64111, in GCC 4.9.3.One of our user's encountered this problem with a
particular file, where the compile time (on arm) went from 20 seconds
to 150 seconds.
On 10/05/2015 05:31 PM, Mikhail Maltsev wrote:
2015-10-05 Mikhail Maltsev
* trans-common.c (create_common): Adjust to use flag_checking.
* trans.c (gfc_add_modify_loc): Use gcc_checking_assert.
I went ahead and did independent testing on this patch, x86_64-linux-gnu
as well as
As requested by Richi, this makes flushing more frequent by always
flushing in execute_todo rather than flushing only after cleaning the CFG.
This slightly improves how often we re-use SSA_NAMEs rather than
allocating new ones. It also allows us to slightly simplify the
release_ssa_names pa
2015-10-24 0:32 GMT+03:00 Jeff Law :
> On 10/23/2015 09:26 AM, Ilya Enkovich wrote:
>>
>> Hi,
>>
>> This patch checks optab exists before using it vector vector statement
>> lowering. It fixes compilation of test from PR68062 with -funsigned-char
>> option added (doesn't fix original testcase). B
This patch fixes a compile-time regression that was originally
introduced by the fix
for PR64111, in GCC 4.9.3.One of our user's encountered this problem with a
particular file, where the compile time (on arm) went from 20 seconds
to 150 seconds.
The fix in this patch was suggested by Richard
On 10/23/2015 09:26 AM, Ilya Enkovich wrote:
Hi,
This patch checks optab exists before using it vector vector statement
lowering. It fixes compilation of test from PR68062 with -funsigned-char
option added (doesn't fix original testcase). Bootstrapped for
x86_64-unknown-linux-gnu. OK for t
On 10/23/2015 01:31 PM, Jakub Jelinek wrote:
> On Fri, Oct 23, 2015 at 01:17:07PM -0700, Cesar Philippidis wrote:
>> Good idea, thanks. This patch also corrects the problems parsing weird
>> combinations of num, static and length arguments that you mentioned
>> elsewhere.
>>
>> Is this OK for trunk
On Fri, Oct 23, 2015 at 10:31:55PM +0200, Jakub Jelinek wrote:
> Doesn't this mean that you happily parse
> gang (static: * abc)
> or
> gang (static:*num:1)
> etc.? I'd say the comma should be non-optional (i.e. either accept
> CPP_COMMA, or CPP_CLOSE_PARENT, but nothing else) in that case (at lea
On 10/23/15 16:17, Cesar Philippidis wrote:
Nathan, can you try out this patch with your updated patch set? I saw
some test cases getting stuck when expanding expand_GOACC_DIM_SIZE in on
the host compiler, which is wrong. I don't see that happening in
gomp-4_0-branch with this patch. Also, can y
On Fri, 2015-10-23 at 15:13 -0600, Jeff Law wrote:
> On 10/23/2015 02:41 PM, David Malcolm wrote:
> > This is a followup to:
> >https://gcc.gnu.org/ml/gcc-patches/2015-09/msg01696.html
> > (one of the individual patches has seen iteration since that, so
> > I'm calling the whole thing "v5" for
On 10/23/2015 02:41 PM, David Malcolm wrote:
This is a followup to:
https://gcc.gnu.org/ml/gcc-patches/2015-09/msg01696.html
(one of the individual patches has seen iteration since that, so
I'm calling the whole thing "v5" for the sake of clarity).
Patches 1-3 are a preamble:
"Improvement
* config/arc/gmon/profil.S (__profil, __profil_irq): Don't profile
Shouldn't profil should return -1 on failure?
config/arc/lib1funcs.S (__udivmodsi4):
@@ -393,7 +393,12 @@ SYM(__udivmodsi4):
lsr_s r1,r1
cmp_s r0,r1
xor.f r2,lp_count,31
+#if !defined (__EM__) && !define
On 10/23/2015 02:41 PM, David Malcolm wrote:
Later on in this patch kit, with token range underlining, the
libstdc++v3 testsuite starts showing numerous failures of the form:
FAIL: 17_intro/using_namespace_std_tr1_neg.cc (test for excess errors)
The excess errors turn out to be the source co
On 10/23/2015 02:41 PM, David Malcolm wrote:
The stats on line-table memory usage emitted via -fmem-report
from input.c's dump_line_table_statistics don't include
information on the ad-hoc data table.
This patch adds lines like this:
Ad-hoc table size: 192k
Ad-hoc table e
On 10/23/2015 02:41 PM, David Malcolm wrote:
libcpp/ChangeLog:
* include/line-map.h (source_location): In the table in the
descriptive comment, show UNKNOWN_LOCATION, BUILTINS_LOCATION,
LINE_MAP_MAX_LOCATION_WITH_COLS, LINE_MAP_MAX_SOURCE_LOCATION.
Add notes about
My patch for 66450 improved a previous problem with clobbering an
existing value for an aggregate, but we still had the problem that the
value in the hash table for the object was different from the value in
ctx->ctor, so changing one didn't update the other. This patch makes
sure they're in s
On 10/23/2015 11:45 AM, Bernd Schmidt wrote:
On 10/23/2015 06:50 PM, Joseph Myers wrote:
On Fri, 23 Oct 2015, Martin Sebor wrote:
But now that I'm re-reading the answer above I see that Joseph
was suggesting that a5_7[5][0] should be diagnosed when the patch
accepts it as an extension. I thin
On Fri, Oct 23, 2015 at 01:17:07PM -0700, Cesar Philippidis wrote:
> Good idea, thanks. This patch also corrects the problems parsing weird
> combinations of num, static and length arguments that you mentioned
> elsewhere.
>
> Is this OK for trunk?
I'd strongly prefer to see always patches accomp
On 10/22/2015 08:00 AM, Jakub Jelinek wrote:
> On Thu, Oct 22, 2015 at 07:47:01AM -0700, Cesar Philippidis wrote:
>>> But it is unclear from the parsing what from these is allowed:
>>
>> int v, w;
>> ...
>> gang(26) // equivalent to gang(num:26)
>> gang(v) // gang(num:v)
>> vector(length: 16) /
On 10/22/2015 01:52 AM, Jakub Jelinek wrote:
> On Wed, Oct 21, 2015 at 03:18:55PM -0400, Nathan Sidwell wrote:
>> This patch is the C++ changes matching the C ones of patch 4. In
>> finish_omp_clauses, the gang, worker, & vector clauses are handled the same
>> as OpenMP's 'num_threads' clause. On
On Fri, Oct 23, 2015 at 02:47:16PM -0500, Segher Boessenkool wrote:
> On Fri, Oct 23, 2015 at 01:22:11PM -0400, Michael Meissner wrote:
> > David asked me to try and break patch #7 into smaller bite sized chunks. I
> > have
> > broken this into roughly 16 parts. These are the same patches that I
The change since v4 can be seen at:
https://dmalcolm.fedorapeople.org/gcc/2015-10-23/0001-Add-colorize_source_p-to-diagnostic_context.patch
which is a tweak to colorization, to handle both frontends that provide
ranges and those that only provide carets, and provide a smoother
transition path for
As in the previous version of this patch
"Implement tree expression tracking in C FE (v2)"
the patch now captures ranges for all C expressions during parsing within
a new field of c_expr, and for all tree nodes with a location_t, it stores
them in ad-hoc locations for later use.
Hence compound ex
The attached patch implements a bit-packing scheme so that short ranges
can be stored directly within a 32-bit source_location (aka location_t)
without needing to use the ad-hoc table. The intent is to mitigate the
overhead introduced in the earlier patch that added ranges for all tokens
in libcpp
A previous patch introduced the ability to print one or more ranges
for a diagnostic via a rich_location class.
Another patch generalized source_location (aka location_t) to be both
a caret and a range, and generated range information for all tokens
coming out of libcpp's lexer.
The attached patc
Some diagnostics e.g. -Wmaybe-uninitialized weren't showing
underlines, despite being provided with range-based data.
Debugging showed that it the pertinent location was an
ad-hoc location with a range:
(gdb) p /x loc
$9 = 0x802a
(gdb) p line_table->location_adhoc_data_map.data[0x2a]
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:
- generalizes the meaning of the source_location (aka location_t) type
from being a caret within the source code to being a caret plus
a source_range. The latter data is stored purely in the ad-hoc data
lookaside for now.
- captures ranges for libcpp tokens by generat
Later on in this patch kit, with token range underlining, the
libstdc++v3 testsuite starts showing numerous failures of the form:
FAIL: 17_intro/using_namespace_std_tr1_neg.cc (test for excess errors)
The excess errors turn out to be the source code and
caret/underlines emitted after an "error"
The stats on line-table memory usage emitted via -fmem-report
from input.c's dump_line_table_statistics don't include
information on the ad-hoc data table.
This patch adds lines like this:
Ad-hoc table size: 192k
Ad-hoc table entries used:4336
OK for trunk?
gcc/
libcpp/ChangeLog:
* include/line-map.h (source_location): In the table in the
descriptive comment, show UNKNOWN_LOCATION, BUILTINS_LOCATION,
LINE_MAP_MAX_LOCATION_WITH_COLS, LINE_MAP_MAX_SOURCE_LOCATION.
Add notes about ad-hoc values.
---
libcpp/include/line-map.h |
This is a followup to:
https://gcc.gnu.org/ml/gcc-patches/2015-09/msg01696.html
(one of the individual patches has seen iteration since that, so
I'm calling the whole thing "v5" for the sake of clarity).
Patches 1-3 are a preamble:
"Improvements to description of source_location in line-map.h
On Fri, Oct 23, 2015 at 01:36:25PM -0400, Michael Meissner wrote:
> This patch allows SUBREG's for the reg_or_indexed_operand, which is used when
> you have an integral value in a float/vector register, and you want to move
> the
> value (either via direct move on power8, or via store).
>
> I hav
On Fri, Oct 23, 2015 at 08:05:58PM +, Joseph Myers wrote:
> On Fri, 23 Oct 2015, Michael Meissner wrote:
>
> > This patch is the new patch from the last submission. It sets up a hook so
> > that
> > the compiler will not allow IBM extended double and IEEE 128-bit floating
> > point
> > to in
On 10/01/2015 04:00 AM, Richard Biener wrote:
Apart from what Jakub said - this keeps the list non-recycled for example
after DCE if that doesnt call cleanup_cfg. Likewise after passes that call
cleanup_cfg manually. It also doesn't get called after IPA transform
passes (which would require ca
On Fri, 23 Oct 2015, Szabolcs Nagy wrote:
> i think bsd libcs do the same, compiler headers interfering
> with libc headers is problematic (e.g. FLT_ROUNDS is wrong
> in gcc float.h, applications shouldn't see that), i'm not sure
FLT_ROUNDS is an ordinary compiler bug (bug 30569), should be fixab
On 10/22/2015 01:22 AM, Jakub Jelinek wrote:
> On Wed, Oct 21, 2015 at 03:16:20PM -0400, Nathan Sidwell wrote:
>> 2015-10-20 Cesar Philippidis
>> Thomas Schwinge
>> James Norris
>> Joseph Myers
>> Julian Brown
>>
>> * c-parser.c (c_parser_oacc_sha
On Fri, 23 Oct 2015, Michael Meissner wrote:
> This patch is the new patch from the last submission. It sets up a hook so
> that
> the compiler will not allow IBM extended double and IEEE 128-bit floating
> point
> to intermix in a binary expression without using an explicit conversion.
I don't
On Fri, Oct 23, 2015 at 01:22:11PM -0400, Michael Meissner wrote:
> David asked me to try and break patch #7 into smaller bite sized chunks. I
> have
> broken this into roughly 16 parts. These are the same patches that I submitted
> for patch #7 (revised), just broken up. There is one additional
On Fri, Oct 23, 2015 at 12:28:14PM -0700, Steve Kargl wrote:
> Built and regression tested on x86_64-*-freebsd.
> OK to commit?
>
Now with the patch attached!
--
Steve
Index: gcc/fortran/array.c
===
--- gcc/fortran/array.c (revisio
All,
The attached patch fixes several ICEs caused by invalid
charlengths. The new testcase pr67805.f90 shows the
kinds of issues the patch will detect. An appropriate
error message is now issued.
Built and regression tested on x86_64-*-freebsd.
OK to commit?
2015-10-23 Steven G. Kargl
On 10/23/2015 03:09 PM, Jeff Law wrote:
On 10/08/2015 07:37 AM, Andrew MacLeod wrote:
On 10/07/2015 06:02 PM, Jeff Law wrote:
On 10/01/2015 08:33 PM, Andrew MacLeod wrote:
these are all in the main gcc directory. 297 files total.
Everything bootstraps on x86_64-pc-linux-gnu and
powerpc64le-un
On 10/23/2015 10:53 AM, Andrew MacLeod wrote:
Just finished running... I think the external hard drive was slowing
down this run :-P It took quite a while.
Anyway, this is the reduction patch independent of the header-ordering
patch... ie, that patch needs to be applied before this one. So t
2015-10-16 Gregor Richards
Szabolcs Nagy
* config.gcc (enable_secureplt): Add *-linux*-musl*.
Okay.
Thanks, David
P.S. Please explicitly copy me on rs6000 patches.
On 10/23/2015 03:15 AM, Richard Biener wrote:
On Fri, Oct 23, 2015 at 8:22 AM, Jeff Law wrote:
/* This is another case of narrowing, specifically when there's an outer
BIT_AND_EXPR which masks off bits outside the type of the innermost
operands. Like the previous case we have to conve
ping.
On 16/10/15 16:48, Szabolcs Nagy wrote:
The musl dynamic loader can only deal with secure-plt,
make it the default.
Split out from
https://gcc.gnu.org/ml/gcc-patches/2015-04/msg01640.html
for easier review (independent of the rest of the patch).
gcc/ChangeLog:
2015-10-16 Gregor Richard
On 10/08/2015 07:37 AM, Andrew MacLeod wrote:
On 10/07/2015 06:02 PM, Jeff Law wrote:
On 10/01/2015 08:33 PM, Andrew MacLeod wrote:
these are all in the main gcc directory. 297 files total.
Everything bootstraps on x86_64-pc-linux-gnu and
powerpc64le-unknown-linux-gnu. All targets in config-l
> 2015-10-16 Gregor Richards
> Szabolcs Nagy
>
> * config/rs6000/linux64.h (MUSL_DYNAMIC_LINKER32): Define.
> (MUSL_DYNAMIC_LINKER64): Define.
> (GNU_USER_DYNAMIC_LINKER32): Update.
> (GNU_USER_DYNAMIC_LINKER64): Update.
> (CHOOSE_DYNAMIC_LINKER): Update.
>
>
On 23/10/15 18:39, Doug Evans wrote:
On Fri, Oct 23, 2015 at 10:08 AM, Bernd Schmidt wrote:
On 10/21/2015 09:00 PM, Doug Evans wrote:
I happened to notice local prefixes not working with musl.
Fixes thusly.
Index: config/linux.h
===
Le 22/10/2015 22:04, Maxim Kuvyrkov a écrit :
Hi,
And this is a similar patch for gfortran.dg/streamio_N.f90 tests.
OK to commit?
Sure.
Mikael
On 10/23/2015 11:31 AM, Bernd Schmidt wrote:
On 10/23/2015 04:57 PM, Simon Dardis wrote:
Patch below. Target hook renamed to
TARGET_NO_SPECULATION_IN_DELAY_SLOTS_P.
Tested on mips-img-elf, no new regressions.
As far as I'm concerned this is ok, and IIUC Jeff was on board too. This
is assumin
Just to follow up on this string, here is a new version of the patch
with the extraneous parenthesis removed.
Steve Ellcey
sell...@imgtec.com
2015-10-23 Steve Ellcey
* frame-header-opt.c (gate): Check for optimize > 0.
(has_inlined_assembly): New function.
(needs_fram
On Fri, Oct 23, 2015 at 01:39:36PM -0400, Michael Meissner wrote:
> This patch prevents the compiler from calling the IEEE 128-bit emulation
> functions with the vector value in both GPRs and vector registers due to the
> fact that the library function did not have a prototype.
>
> I have built th
This patch adds a test to make sure __float128 are passed and returned like
vector objects, and not as IBM extended double did.
This is the last subpatch of patch #7. I have bootstrapped the compiler with
all 16 subpatches installed, and there were no regressions. Is it ok to
install in the trun
This patch adds the documentation.
I have built the compiler with this patch and the previous subpatches (1-14).
I have bootstrapped the compiler with all 16 subpatches installed, and there
were no regressions. Is it ok to install in the trunk?
2015-10-22 Michael Meissner
* doc/exten
This patch makes TFmode be fully switchable for comparisons.
I have built the compiler with this patch and the previous subpatches (1-13).
I have bootstrapped the compiler with all 16 subpatches installed, and there
were no regressions. Is it ok to install in the trunk?
2015-10-22 Michael Meiss
This patch is the second part to allow TFmode to be IBM extended double or IEEE
128-bit floating point depending on switches.
I have built the compiler with this patch and the previous subpatches (1-12).
I have bootstrapped the compiler with all 16 subpatches installed, and there
were no regressio
This patch is the first of two rs6000.md patches to straighten out the IFmode,
KFmode, and TFmode support. Part of the change is to change the iterator names
to be easier to understand, using IEEE128, IBM128, and FLOAT128 as the
iterators. This change, and the next change go through and have para
This patch changes the mangling for __float128. I came to the conclusion that
the current code is so tangled, that it would be better to use U10__float128
rather than "e". However, if it is felt that we should go with "e", I can go
that way as well.
I have built the compiler with this patch and
This patch is part of the support needed to properly swap IEEE 128-bit floating
point on little endian systems. Note, you will need the rs6000.md changes for
this to become effective.
I have built the compiler with this patch and the previous subpatches (1-9). I
have bootstrapped the compiler wi
On 30/09/15 11:42, Claudiu Zissulescu wrote:
This patch adds basic support for Synopsys' ARCv2 CPUs.
There is an awful lot of places that have TARGET_ARC700 || TARGET_V2 etc.
Maybe it's time for some new feature-oriented macros? Like:
TARGET_ARC600_FAMILY ARC600 and ARC601, for ARC600 pip
This patch is the new patch from the last submission. It sets up a hook so that
the compiler will not allow IBM extended double and IEEE 128-bit floating point
to intermix in a binary expression without using an explicit conversion.
I have built the compiler with this patch and the previous subpat
On Oct 23, 2015, at 10:36 AM, Andrew MacLeod wrote:
>
> darwin-driver.c had some code that depended on one of the include files, bit
> no other part of the file needed it, so that was the issue there. The only
> other place it seems could be an issue is with collect2.c... so I'll monitor
> th
This patch adds support for using 'q' or 'Q' as a suffix for __float128
constants, which is compatible with the existing x86_64 implmenetation of their
__float128 support.
I have built the compiler with this patch and the previous subpatches (1-7). I
have bootstrapped the compiler with all 16 sub
On 10/23/2015 06:50 PM, Joseph Myers wrote:
On Fri, 23 Oct 2015, Martin Sebor wrote:
But now that I'm re-reading the answer above I see that Joseph
was suggesting that a5_7[5][0] should be diagnosed when the patch
accepts it as an extension. I think we do want to accept it
because a5_7 is trea
This patch updates to use the unordered comparison function for IEEE 128-bit
floating point to mimic the behaviour of SFmode/DFmode using the fcmpu
instruction.
It also restructures the code to allow a future change to drop in easier.
I have built the compiler with this patch and the previous sub
On 10/23/2015 07:36 PM, Doug Evans wrote:
The only significant different AFAICT is that GCC_INCLUDE_DIR is moved
to later (last).
Why this is is briefly described in the intro comment:
config/linux.h:
/* musl avoids problematic includes by rearranging the include
directories.
* Unfortunat
This patch sets up all of the emulation functions.
I have built the compiler with this patch and the previous subpatches (1-4). I
have bootstrapped the compiler with all 16 subpatches installed, and there were
no regressions. Is it ok to install in the trunk?
2015-10-22 Michael Meissner
On Fri, Oct 23, 2015 at 10:08 AM, Bernd Schmidt wrote:
>
> On 10/21/2015 09:00 PM, Doug Evans wrote:
>>
>> I happened to notice local prefixes not working with musl.
>> Fixes thusly.
>
>
>> Index: config/linux.h
>> ===
>> --- config/l
This patch prevents the compiler from calling the IEEE 128-bit emulation
functions with the vector value in both GPRs and vector registers due to the
fact that the library function did not have a prototype.
I have built the compiler with this patch and the previous subpatches (1-4). I
have bootst
On Oct 23, 2015, at 10:24 AM, Bernd Schmidt wrote:
> On 10/23/2015 07:15 PM, Mike Stump wrote:
>> On Oct 23, 2015, at 9:57 AM, Bernd Schmidt
>> wrote:
>>>
>>> I'm guessing it's the CROSS_DIRECTORY_STRUCTURE macro which is used
>>> by darwin targets. It's also used for several other targets, so y
On 10/23/2015 01:24 PM, Bernd Schmidt wrote:
On 10/23/2015 07:15 PM, Mike Stump wrote:
On Oct 23, 2015, at 9:57 AM, Bernd Schmidt
wrote:
I'm guessing it's the CROSS_DIRECTORY_STRUCTURE macro which is used
by darwin targets. It's also used for several other targets, so you
may want to double c
This patch allows SUBREG's for the reg_or_indexed_operand, which is used when
you have an integral value in a float/vector register, and you want to move the
value (either via direct move on power8, or via store).
I have built the compiler with this patch and the previous subpatches (1-3). I
have
On Fri, 23 Oct 2015, Jakub Jelinek wrote:
> Thus, if .shared function local is allowed, we'd need to emit two copies of
> foo, one which assumes it is run in the teams context and one which assumes
> it is run in the parallel context. If automatic vars can be only .local,
> we are just in big trou
On Fri, Oct 23, 2015 at 1:52 AM, Richard Biener
wrote:
> On Thu, Oct 22, 2015 at 7:09 PM, H.J. Lu wrote:
>> When -Bsymbolic is passed to linker, references to global symbols
>> defined in the shared library are resolved locally. We should pass
>> -fsymbolic to GCC in this case.
>
> Hmm, I think
This patch defines 3 macros to tell the user whether -mfloat128 is enabled or
not, and whether long double is IBM extended double or IEEE 128-bit floating
point.
I have built the compiler with this patch and the previous subpatches (1 and
2). I have bootstrapped the compiler with all 16 subpatche
On 10/23/2015 04:57 PM, Simon Dardis wrote:
Patch below. Target hook renamed to TARGET_NO_SPECULATION_IN_DELAY_SLOTS_P.
Tested on mips-img-elf, no new regressions.
As far as I'm concerned this is ok, and IIUC Jeff was on board too. This
is assuming the test included a bootstrap, otherwise pl
This patch changes the switch from -mfloat128-software and -mfloat128-none to
be a binary switch, -mfloat128 and -mno-float128. It also provides some of the
basic setup for IEEE types. It also removes code I had put in a previous patch
that doesn't allow IFmode/KFmode to go in any register if -mn
This patch is the rs6000.h changes. It makes the IEEE 128-bit floating point
type that can go in vector registers a 'vector' type, so that the address code
in rs6000.c that determines whether to use VSX addressing works. In addition, I
made IEEE 128-bit floating point tie with vectors and not with
On 10/23/2015 07:15 PM, Mike Stump wrote:
On Oct 23, 2015, at 9:57 AM, Bernd Schmidt
wrote:
I'm guessing it's the CROSS_DIRECTORY_STRUCTURE macro which is used
by darwin targets. It's also used for several other targets, so you
may want to double check those.
No, only darwin is special, as p
> [ added missing cc of gcc-patches ]
>
> On 23/10/15 17:46, Tom de Vries wrote:
> >[ Quote-pasted from
> >https://gcc.gnu.org/ml/gcc-patches/2012-01/msg01077.html ]
> >
> >>The LTO bootstrap of the Ada compiler is currently plagued by at least
> >>three
> >>different problems. The attached patch
David asked me to try and break patch #7 into smaller bite sized chunks. I have
broken this into roughly 16 parts. These are the same patches that I submitted
for patch #7 (revised), just broken up. There is one additional patch in this
selection, to restrict __float128 and IBM extended double fro
On Oct 23, 2015, at 9:57 AM, Bernd Schmidt wrote:
>
> I'm guessing it's the CROSS_DIRECTORY_STRUCTURE macro which is used by darwin
> targets. It's also used for several other targets, so you may want to double
> check those.
No, only darwin is special, as presently only darwin has the requisi
On 10/21/2015 09:00 PM, Doug Evans wrote:
I happened to notice local prefixes not working with musl.
Fixes thusly.
Index: config/linux.h
===
--- config/linux.h(revision 229130)
+++ config/linux.h(working copy)
@@ -174,6 +1
On 10/22/2015 02:25 PM, Richard Henderson wrote:
I believe I've addressed all of your comments like so.
This looks much better, except for this hunk:
diff --git a/gcc/doc/extend.texi b/gcc/doc/extend.texi
index e54fe67..5793868 100644
--- a/gcc/doc/extend.texi
+++ b/gcc/doc/extend.texi
@@ -12
On 10/22/2015 01:58 AM, Richard Biener wrote:
On Thu, Oct 22, 2015 at 5:12 AM, Sandra Loosemore
wrote:
On 10/20/2015 03:27 PM, Richard Henderson wrote:
+@deftypefn {Target Hook} bool TARGET_ADDR_SPACE_ZERO_ADDRESS_VALID
(addr_space_t @var{as})
+Define this to modify the default handling of a
I am checking in this patch to update my email address. The sell...@mips.com
address still works but I have been using sell...@imgtec.com recently as
that is more 'official'.
Steve Ellcey
sell...@imgtec.com
2015-10-23 Steve Ellcey
* MAINTAINERS: Update email address.
diff --git
> can isl-0.15 be built with 4.8 and 4.9? ..with an old libc?
isl-0.15 builds for me with gcc 4.6.4, 4.7.4, 4.8.3, 4.9.2, not sure about
older libc.
I can't find any reference to max_align_t in the isl-0.15 source.
(for me actually also isl-0.14 builds fine down to gcc 4.6).
Maybe somebody with
1 - 100 of 202 matches
Mail list logo
