2013/11/24 Mike Stump :
> Richi has asked the we break the wide-int patch so that the individual port
> and front end maintainers can review their parts without have to go through
> the entire patch.This patch covers the nds32 port.
>
> Ok?
>
OK.
The changes are straightforward on using wid
On 11/22/2013, 8:04 PM, dxq wrote:
fixing SMS, do you mean that we only modify the SMS pass?
You don't need loop unrolling when you have a good software pipelining
and loop vectorization. A good software pipelining can see through any
number of iterations and has no problems with code cache l
---
ChangeLog entry:
2013-11-24 Josh Triplett
* output.h (get_named_text_section): Fix typo in comment:
s/SECITON/SECTION/
gcc/output.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/gcc/output.h b/gcc/output.h
index 7b26256..3a86e1b 100644
--- a/gcc/o
Oleg Endo wrote:
> This is a small SH cleanup patch. No functional changes -- at least not
> intended.
>
> The ROUND_ADVANCE macro can be replaced with CEIL from system.h, which
> makes it a bit clearer towards what something is rounded in the places
> where it's used.
>
> The ROUND_REG and PAS
Oleg Endo wrote:
> Currently GCC doesn't pass the --isa parameter to the assembler for SH
> targets other than SH2A and SH5. This makes the assembler accept any
> kind of ISA and happily produce e.g. SH2A code even though the target is
> SH4, which will then fail to link.
> The attach patch fixes
On 11/24/2013 08:38 AM, N.M. Maclaren wrote:
On Nov 24 2013, Kenneth Zadeck wrote:
Thank you for your posting. That certainly clears up my understanding.
If there is a clear description of the subset
of C++ that the front-end is allowed to use, a pointer to it for the
benefit of Fortran/C/Ad
Hi Janus,
Janus Weil wrote:
+ else if (ref->type == REF_COMPONENT &&
ref->u.c.component->attr.function
+ && ref->u.c.component->attr.proc_pointer
+ && ref->u.c.component->attr.dimension)
I wonder whether one should take care of functions returning BT_CLASS,
but
Hello,
This is a small SH cleanup patch. No functional changes -- at least not
intended.
The ROUND_ADVANCE macro can be replaced with CEIL from system.h, which
makes it a bit clearer towards what something is rounded in the places
where it's used.
The ROUND_REG and PASS_IN_REG_P macros (origina
On Sun, Nov 24, 2013 at 9:39 PM, H.J. Lu wrote:
> I opened:
>
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59279
Thanks for the report. I can't reproduce it on powerpc64.
This isn't the time to leave the trunk broken, so I've reverted the
patch for now.
Ciao!
Steven
Hi Tobias,
>> here is a straightforward patch to teach 'get_expr_storage_size' about
>> type-bound procedures (which are handled internally as
>> procedure-pointer components of the corresponding vtab). In that sense
>> the patch should handle both TBPs as well as PPCs.
>>
>> Regtested on x86_64-u
On Sun, Nov 24, 2013 at 12:26 PM, H.J. Lu wrote:
> On Wed, Nov 20, 2013 at 12:59 PM, Steven Bosscher
> wrote:
>> Hello,
>>
>> With the attached patch, dead jump tables are deleted if a
>> CLEANUP_EXPENSIVE is performed in cfglayout mode. This helps remove
>> labels and merge basic blocks, and br
On Wed, Nov 20, 2013 at 12:59 PM, Steven Bosscher wrote:
> Hello,
>
> With the attached patch, dead jump tables are deleted if a
> CLEANUP_EXPENSIVE is performed in cfglayout mode. This helps remove
> labels and merge basic blocks, and brings the CFG out of cfglayout
> mode more cleanly. It also f
Thomas, what's actually the status of this patch? I think it was
half-complete in September.
Tobias
On September 4, 2013 12:40, Janne Blomqvist wrote:
On Tue, Sep 3, 2013 at 3:04 PM, Thomas Koenig wrote:
Hello world,
here is a rewrite, which I hope make things more clear.
Unformatted sequen
OK.
Jason
On Sat, 2013-04-27 at 08:56 +0100, Richard Sandiford wrote:
> Yeah, I think so. If "=>" mean "accepts more than", then there used
> to be a nice total order:
>
> next_insn
> => next_nonnote_insn
> => next_real_insn
> => next_active_insn
Hi Richard,
This (plus inevitable fixes in back
Hi!
For my Build Robot, I'd like to change contrib/config-list.mk to be
more generally useable. This patch allows to override the defaults for
$(host_options), which currently mentions mpc's location.
The second change allows to print the list of buildable targets,
which saves me the need to to
Besides all changes to .cc/.h files in libsanitizer should go thorough
the upstream repo first
and I generally dislike the change in
libsanitizer/sanitizer_common/sanitizer_symbolizer_posix_libcdep.cc,
we'll need to find another solution (using libbacktrace could be one;
I am not so enthusiastic ab
On Sun, Nov 24, 2013 at 10:20:18AM -0800, H.J. Lu wrote:
> Hi,
>
> This patch adds --enable-llvm-symbolizer and disables llvm-symbolizer by
> default. Without it, GCC sanitizer is unusable on systems with
> unsupported /bin/llvm-symbolizer. OK to install?
See http://gcc.gnu.org/ml/gcc-patches/2
Hi,
This patch adds --enable-llvm-symbolizer and disables llvm-symbolizer by
default. Without it, GCC sanitizer is unusable on systems with
unsupported /bin/llvm-symbolizer. OK to install?
Thanks.
H.J.
2013-11-24 H.J. Lu
PR sanitizer/59136
* configure.ac: Add --enable-llvm-
Ok.
David
On Sun, Nov 24, 2013 at 6:50 AM, Teresa Johnson wrote:
> The current default is 300, but increasing to 4M gives better
> performance on internal applications and benchmarks. Passes regression
> testing. Ok for google/4_8?
>
> Thanks,
> Teresa
>
> 2013-11-24 Teresa Johnson
>
>
gcc/cp/
PR c++/59112
PR c++/59113
* parser.c (cp_parser_parameter_declaration_clause): Disallow implicit
function templates in local functions unless defining a lambda.
gcc/testsuite/
PR c++/59112
PR c++/59113
g++.dg/cpp1y/pr58533.C: Updated
Hello,
Currently GCC doesn't pass the --isa parameter to the assembler for SH
targets other than SH2A and SH5. This makes the assembler accept any
kind of ISA and happily produce e.g. SH2A code even though the target is
SH4, which will then fail to link.
The attach patch fixes this by passing the
On Sun, 2013-11-24 12:14:19 +0100, Gerald Pfeifer wrote:
> On Sat, 23 Nov 2013, Jan-Benedict Glaw wrote:
> > +Toolchain Build Robot
> > +[2013-11-23]
> > +The http://toolchain.lug-owl.de/buildbot/";>Build
> > Robot is
> > + mass-compiling GCC (stage1 only) using contrib/config-list.m
I am not sure about the lsan part. Sergey?
The rest looks good.
On Sun, Nov 24, 2013 at 8:44 PM, Tobias Burnus wrote:
> As the subject says.
>
> OK for the trunk?
>
> Tobias
As the subject says.
OK for the trunk?
Tobias
2013-11-24 Tobias Burnus
PR sanitizer/59275
* doc/invoke.texi (-fsanitize=address,leak): Mention the associated
environment variable and link to a list with flags.
(-fsanitize=thread): Ditto and update link.
diff --git a/gcc/doc/invoke.texi
Committed as obvious: Rev. 205336.
Tobias
2013-11-24 Tobias Burnus
* doc/invoke.texi (-fsanitize=leak): Add link to the wiki page.
diff --git a/gcc/doc/invoke.texi b/gcc/doc/invoke.texi
index f00bbf2..1afc9e3 100644
--- a/gcc/doc/invoke.texi
+++ b/gcc/doc/invoke.texi
@@ -5279,3 +5279,4 @@ M
On Sun, Nov 24, 2013 at 2:38 PM, N.M. Maclaren wrote:
> The main problem is that integer constant expressions in C are limited to
> the built-in operators, of which the only tricky ones are division and
> remainder (and, occasionally, multiplication) - see C11 6.6#3. Fortran
> is not so limited, a
Janus Weil wrote:
here is a straightforward patch to teach 'get_expr_storage_size' about
type-bound procedures (which are handled internally as
procedure-pointer components of the corresponding vtab). In that sense
the patch should handle both TBPs as well as PPCs.
Regtested on x86_64-unknown-li
On Sun, 24 Nov 2013, Florian Weimer wrote:
On 11/12/2013 04:22 PM, Marc Glisse wrote:
On Tue, 12 Nov 2013, Ondřej Bílka wrote:
Anyway you need a better analysis to determine if user called realloc on
converted pointer.
Note that I am checking if the argument of free is the same as the
retur
Am 24.11.2013 13:56, schrieb Kenneth Zadeck:
On 11/24/2013 05:50 AM, Tobias Burnus wrote:
- if (hi || low < 0
...
+ if (((!as || as->type != AS_ASSUMED_RANK)
+ && wi::geu_p (bound, GFC_TYPE_ARRAY_RANK (TREE_TYPE (desc
+ || wi::gtu_p (bound, GFC_MAX_DIMENSIONS))
gfc_error ("'dim' argument of
On Thu, Nov 21, 2013 at 11:37 AM, Jakub Jelinek wrote:
> On Thu, Nov 21, 2013 at 07:43:35AM +1000, Richard Henderson wrote:
>> On 11/20/2013 07:44 PM, Jakub Jelinek wrote:
>> > On Wed, Nov 20, 2013 at 10:31:38AM +0100, Richard Biener wrote:
>> >> Aww ;) Nice improvement. Generally when I see thi
Hi,
This patches gen_compile_unit_die to use the DW_LANG_D DWARF language
code for D. Is in relation to some other D language fixes that are
going to be submitted to gdb.
Regards
Iain.
diff --git a/gcc/dwarf2out.c b/gcc/dwarf2out.c
index 3448ec4..ddbf5de 100644
--- a/gcc/dwarf2out.c
+++ b/gcc/dw
> Everything is clean on SPARC/Solaris and SPARC64/Solaris as well so I have
> no objections to backporting the whole set from a SPARC maintainership
> viewpoint (and we have been using something equivalent at AdaCore for some
> time without any problems so far). But we need the blessing of the RM
The current default is 300, but increasing to 4M gives better
performance on internal applications and benchmarks. Passes regression
testing. Ok for google/4_8?
Thanks,
Teresa
2013-11-24 Teresa Johnson
* params.def (PARAM_MAX_LIPO_MEMORY): Increase default to 4M.
Index: params.de
> OK. Thanks for the patch!
Committed as rev. 205335.
ping!
2013/11/18 Janus Weil :
> Hi all,
>
> here is a straightforward patch to teach 'get_expr_storage_size' about
> type-bound procedures (which are handled internally as
> procedure-pointer components of the corresponding vtab). In that sense
> the patch should handle both TBPs as well as PPCs.
Hi FX,
>>> A quick grep through the front-end indicates that
>>> gfc_open_intrinsic_module() is never used. Should it have been
>>> removed when module file reading/writing was overhauled?
>>
>> I suspect the answer is "yes”.
>
> Here’s a patch that removes it. It buils fine.
> OK to commit?
OK.
On Sun, Nov 24, 2013 at 5:29 AM, H.J. Lu wrote:
> On Tue, Nov 19, 2013 at 7:19 PM, H.J. Lu wrote:
>> On Tue, Nov 19, 2013 at 7:01 AM, Richard Biener wrote:
>>>
>>> $subject - the following turns
>>>
>>> loop_iterator li;
>>> FOR_EACH_LOOP (li, loop, LI_ONLY_INNERMOST)
>>>{
>>> ...
>>>
Hi,
On 2013-11-24 22:38, N.M. Maclaren wrote:
The main problem is that integer constant expressions in C are limited to
the built-in operators, of which the only tricky ones are division and
remainder (and, occasionally, multiplication) - see C11 6.6#3. Fortran
is not so limited, and there are
On 11/23/2013 09:55 PM, Kenneth Zadeck wrote:
On 11/23/2013 08:47 PM, Jason Merrill wrote:
So if the target supports wide ints you'll always use the scalar float
code? Why does that do the right thing?
if TARGET_SUPPORTS_WIDE_INT != 0, then integers are NEVER placed in
const-doubles. larg
On Nov 24 2013, Kenneth Zadeck wrote:
Thank you for your posting. That certainly clears up my understanding.
If there is a clear description of the subset
of C++ that the front-end is allowed to use, a pointer to it for the
benefit of Fortran/C/Ada/whatever people would be useful. But that's
On Tue, Nov 19, 2013 at 7:19 PM, H.J. Lu wrote:
> On Tue, Nov 19, 2013 at 7:01 AM, Richard Biener wrote:
>>
>> $subject - the following turns
>>
>> loop_iterator li;
>> FOR_EACH_LOOP (li, loop, LI_ONLY_INNERMOST)
>>{
>> ...
>> if ()
>>FOR_EACH_LOOP_BREAK;
>>}
>>
>> int
On 11/23/2013 07:22 PM, Mike Stump wrote:
> java:
> * boehm.c: Include wide-int.h.
> (mark_reference_fields): Use a wide_int mask.
> (get_boehm_type_descriptor): Use wide-int interfaces.
> * expr.c: Include wide-int.h.
> (build_newarray): Remove bogus "== INTEGER_CST".
On 11/12/2013 04:22 PM, Marc Glisse wrote:
On Tue, 12 Nov 2013, Ondřej Bílka wrote:
Anyway you need a better analysis to determine if user called realloc on
converted pointer.
Note that I am checking if the argument of free is the same as the
return value of malloc by looking at the SSA_NAME,
Graham Stott writes:
> The attached patch adds support for MSA instructions (MIPS SIMD
> ARCHITECTURE) V1.07
>
> I working on a ChangeLog to go with patch.
>
> I wanted to get the patch out for comments.
>
> The patch is against todays SVN 205118
Sorry, one further thing on top of the other mes
>> A quick grep through the front-end indicates that
>> gfc_open_intrinsic_module() is never used. Should it have been
>> removed when module file reading/writing was overhauled?
>
> I suspect the answer is "yes”.
Here’s a patch that removes it. It buils fine.
OK to commit?
FX
a.ChangeLog
Des
On 11/24/2013 05:50 AM, Tobias Burnus wrote:
Mike Stump wrote:
Richi has asked the we break the wide-int patch so that the
individual port and front end maintainers can review their parts
without have to go through the entire patch.This patch covers the
fortran front end.
Nice clean up.
On 11/24/2013 05:16 AM, N.M. Maclaren wrote:
On Nov 23 2013, Andrew Pinski wrote:
On Sat, Nov 23, 2013 at 12:16 PM, Steve Kargl
wrote:
On Sat, Nov 23, 2013 at 11:21:21AM -0800, Mike Stump wrote:
Richi has asked the we break the wide-int patch so that the
individual port and front end maint
On 11/24/2013 05:47 AM, Uros Bizjak wrote:
On Sun, Nov 24, 2013 at 11:23 AM, Kenneth Zadeck
wrote:
We did not do this kind of transformation for any port beyond the minimum of
having the port use wide-int rather than double-int. we did do a lot of this
in the common code, especially in the
On 24 November 2013 02:57, Kenneth Zadeck wrote:
> if the compiler produced an error message about not finding something, we
> added the include.
If you can't tell what you need/should include by what you use, that
leads to fragile design.
> It is possible that some of these may be redundant a
Uros Bizjak writes:
> - * gcc.dg/ira-shrinkwrap-prep-1.c: Also tes ppc64, changed all ints
> -to longs.
> + * gcc.dg/ira-shrinkwrap-prep-1.c: Also test ppc64, chang all ints
s/chang/change/
Andreas.
--
Andreas Schwab, sch...@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53
On Sat, 23 Nov 2013, Jan-Benedict Glaw wrote:
> Now that it's nicely working, I'd like to publically announce the
> Build Robot. As suggested, here's a patch adding it to GCC's
> homepage's "Development" section as well as to the "News":
Agreed.
> +Toolchain Build Robot
> +[2013-11-23]
> +
Mike Stump wrote:
Richi has asked the we break the wide-int patch so that the individual port and
front end maintainers can review their parts without have to go through the
entire patch.This patch covers the fortran front end.
Nice clean up. The new class looks much cleaner as it avoids
On Sun, Nov 24, 2013 at 11:23 AM, Kenneth Zadeck
wrote:
> We did not do this kind of transformation for any port beyond the minimum of
> having the port use wide-int rather than double-int. we did do a lot of
> this in the common code, especially in the code that was just not correct for
> ty
Tobias Burnus wrote:
While looking at the index for -fsanitize=, I found out that it – and
many other options – lack the @opindex. Attached is an attempted to
add the missing ones.
Updated patch: I also observed some odd "*<-fsanitize=null>" output in
the man page; Manuel suggested a fix whic
We did not do this kind of transformation for any port beyond the minimum of
having the port use wide-int rather than double-int. we did do a lot of this
in the common code, especially in the code that was just not correct for types
beyond 64 bits.
Our motivation was that this is already a hu
On Nov 23 2013, Andrew Pinski wrote:
On Sat, Nov 23, 2013 at 12:16 PM, Steve Kargl
wrote:
On Sat, Nov 23, 2013 at 11:21:21AM -0800, Mike Stump wrote:
Richi has asked the we break the wide-int patch so that the individual
port and front end maintainers can review their parts without have to
Hello!
Attached patch fixes compile failure and adds ieee options due to
denormal values in the testcase.
2013-11-23 Uros Bizjak
* gcc.dg/float-exact-1.c: Use dg-add-options ieee.
[LDBL_MANT_DIG == 113]: Fix wrong variable name.
Tested on alphaev68-linux-gnu and committed to mainline
Hi all,
attached is an updated version of the patch.
Change:
Tobias Burnus wrote:
But for "USE mod_name, only: nml", one is supposed to generate a
DW_TAG_imported_declaration. And there I am stuck. For normal
variables, the DW_TAG_imported_declaration refers to a DW_TAG_variable
die. Analogo
On Sat, Nov 23, 2013 at 8:22 PM, Mike Stump wrote:
> Richi has asked the we break the wide-int patch so that the individual port
> and front end maintainers can review their parts without have to go through
> the entire patch.This patch covers the i386 port.
Should this patch also address c
60 matches
Mail list logo
