On 14/7/26 11:28 AM, Chen Gang wrote:
> The related strncpy() for custom_builtin_name[*] may set 5 none-zero
> characters, which may cause custom_builtin_name[*] is none-zero
> terminated.
>
> So add additional '\0' byte for custom_builtin_name[*].
Where did you see this? Supposedly the snprintf
Tom Tromey writes:
>> "Samuel" == Samuel Bronson writes:
>
> Samuel> +# FIXME: The handling of e.g. std::basic_string (at least on char)
> Samuel> +# probably needs updating to work with Python 3's new string rules.
> Samuel> +#
> Samuel> +# In particular, Python 3 has a separate type (calle
The related strncpy() for custom_builtin_name[*] may set 5 none-zero
characters, which may cause custom_builtin_name[*] is none-zero
terminated.
So add additional '\0' byte for custom_builtin_name[*].
ChangeLog:
* config/nios2/nios2.c (custom_builtin_name): Let it always be
zero
The related strncpy() for custom_builtin_name[*] may set 5 none-zero
characters, which cause custom_builtin_name[*] none-zero terminated.
But error() assumes custom_builtin_name[*] is always zero terminated.
So add additional '\0' byte for custom_builtin_name[*].
ChangeLog:
* config/nios
On 07/26/2014 05:12 AM, Jeff Law wrote:
> On 07/23/14 16:17, Chen Gang wrote:
>> On 07/23/2014 11:44 AM, Jeff Law wrote:
>>> On 07/21/14 09:47, Chen Gang wrote:
'asm_out_file' may be 'stdout', so need check this case before close
it.
Or 'stdout' may be closed -- since need not open
The patch has been motivated by the needs for implementing the openacc
module. In particular, it does:
- Fix passing intrinsic types to CLASS(*) [F2003]
- Fix STORAGE_SIZE for polymorphic arrays [F2003]
- Permit the vendor intrinsic SIZEOF also for TYPE(*) if and only if an
array descriptor has
Ok. The internal benchmark testing also shows no change in behavior.
David
On Fri, Jul 25, 2014 at 2:55 PM, Jeff Law wrote:
> On 07/23/14 15:52, Xinliang David Li wrote:
>>
>> Index: ChangeLog
>> ===
>> --- ChangeLog (revision 212
Individual users will still have to:
1. Install git-merge-changelog
2. Set up the merge driver in their git config
See gnulib's lib/git-merge-changelog.c [1] for details.
For example, I:
1. Patched Debian's gnulib package to build git-merge-changelog, and
sent the patch to the Debian ma
On 07/19/14 14:05, Richard Sandiford wrote:
IRA (like the old allocators) calculates a "best" class and an "alternative"
class for each allocno. The best class is the one with the lowest cost while
the alternative class is the biggest class whose cost is smaller than the
cost of spilling. When
On 07/23/14 02:53, Kyrill Tkachov wrote:
Darn, had forgotten to attach the patch...
On 16/07/14 12:30, Kyrill Tkachov wrote:
Hi all,
This fixes the PR mentioned in the subject. When expanding
atomic_test_and_set we try the corresponding sync optabs and if none
exist, like for pre-SMP ARM arch
On Tue, 15 Jul 2014, Michael Meissner wrote:
> These patches are the PowerPC specific patches to add IEEE 128-bit support to
> libgcc. These patches need to be co-ordinated with the glibc support that
> provides the software floating point emulation. The compiler patches need to
> be installed b
On 07/23/14 02:54, Kyrill Tkachov wrote:
2014-07-16 Kyrylo Tkachov
James Greenhalgh
* doc/md.texi (clrsb): Document.
(clz): Change reference to x into operand 1.
(ctz): Likewise.
(popcount): Likewise.
(parity): Likewise.
The second version s
On 07/23/14 15:52, Xinliang David Li wrote:
Index: ChangeLog
===
--- ChangeLog (revision 212682)
+++ ChangeLog (working copy)
@@ -1,3 +1,10 @@
+2014-07-16 Xinliang David Li
+
+ * params.def: New parameter.
+ * covera
On Tue, 15 Jul 2014, Michael Meissner wrote:
> This patch is the machine independent patch for libgcc to add IEEE 128-bit
> floating point to the PowerPC.
>
> This patch allows the PowerPC port to override the TFtype in quad.h to allow
> it
> to use __float128 instead of attribute ((TF)). On mo
On 07/25/2014 05:21 PM, Jakub Jelinek wrote:
On Fri, Jul 25, 2014 at 04:41:08PM -0400, Jason Merrill wrote:
On 07/04/2014 04:47 PM, Jakub Jelinek wrote:
(ubsan_expand_null_ifn): ...take type from ckind argument's type rather
than
first argument.
Why? It looks like they have
On 07/24/14 03:35, Richard Biener wrote:
The following fixes one of the most annoying parts of non-working -ftrapv,
namely that we only support >= word_mode trappings (quite annoying on
64bit archs where 'int' is not handled). At least on x86_64 libgcc
has all the libfuncs available for SImode
On 07/25/2014 07:43 AM, Braden Obrzut wrote:
This patch only covers constexpr variable templates, so it makes sense
to produce an error for now.
Fair enough, but in that case let's use 'sorry' rather then 'error' to
be clear that it's a missing feature.
I ran the testsuite with your patch ap
On 07/24/14 03:11, Kyrill Tkachov wrote:
Ping.
https://gcc.gnu.org/ml/gcc-patches/2014-07/msg00958.html
Kyrill
On 14/07/14 11:01, Kyrill Tkachov wrote:
On 11/07/14 14:20, Alexander Monakov wrote:
On Fri, 11 Jul 2014, Kyrill Tkachov wrote:
On 10/07/14 22:53, Maxim Kuvyrkov wrote:
The patch l
On Fri, Jul 25, 2014 at 04:41:08PM -0400, Jason Merrill wrote:
> On 07/04/2014 04:47 PM, Jakub Jelinek wrote:
> > (ubsan_expand_null_ifn): ...take type from ckind argument's type rather
> > than
> > first argument.
>
> Why? It looks like they have the same type with your patch, and then
On 07/23/14 07:15, Marek Polacek wrote:
Bultin macros like __FILE__, __DATE__, etc. had wrong locus - always
column 1. This patch fixes it by giving those macros location
of the expansion point, i.e, the location, where builtin macro is used.
It now also does the correct thing if we do e.g.
#def
On 07/23/14 11:49, Marek Polacek wrote:
On Thu, Jul 17, 2014 at 02:40:27AM -0600, Jeff Law wrote:
I was really hoping someone could add tests from the old (2004?) thread
between DJ and Per to ensure we weren't regressing any of those cases while
fixing 57653. In fact, I think I'd pre-approved w
On 07/23/14 16:17, Chen Gang wrote:
On 07/23/2014 11:44 AM, Jeff Law wrote:
On 07/21/14 09:47, Chen Gang wrote:
'asm_out_file' may be 'stdout', so need check this case before close it.
Or 'stdout' may be closed -- since need not open 'stdout', either need
not close it.
ChangLog:
* topleve
Il 24/07/2014 19:32, Uros Bizjak ha scritto:
> Hello!
>
>> Well, I was lucky enough to gain access to an alpha pca56 for a day (I say
>> lucky, this may not be repeatable!). However I was not able to build the Ada
>>
>> frontend, due (AFAICT) to the image being too big for relocations.
>> (Moreov
Hi
I think I never get feedback regarding this patch proposal. Note
that if accepted the doc will have to be updated regarding the default
hint value.
Thanks
On 03/06/2014 22:44, François Dumont wrote:
Hi
Thanks to the single bucket introduced to make move semantic
noexcept we ca
On Wed, 9 Jul 2014, Mingjie Xing wrote:
> 2014-07-09 Mingjie Xing
>
> * texi2pod.pl (postprocess): Move command process for '@sc' to the
> front of '@dfn'. Add a new command process for '@t{...}', just print
> the content.
OK.
--
Joseph S. Myers
jos...@codesourcery.
On 07/04/2014 04:47 PM, Jakub Jelinek wrote:
(ubsan_expand_null_ifn): ...take type from ckind argument's type rather
than
first argument.
Why? It looks like they have the same type with your patch, and then
you need to convert ckind back to unsigned char.
Jason
On 07/24/14 09:44, Richard Sandiford wrote:
Three targets had the same for_each_rtx function to check for a TLS symbol.
This patch adds a generic version instead.
Some other targets have a variation that checks for target-specific
UNSPEC sequences too so I've left those alone. They're all prefi
The attached patch is identical to v2 except that I rebased it over
the current head.
To recollect, GDB now supports xmethods in its Python API:
https://sourceware.org/gdb/current/onlinedocs/gdb/Xmethods-In-Python.html
This feature will be available in GDB starting version 7.8 (which has
not yet
On Wed, 2014-07-23 at 15:06 -0500, Peter Bergner wrote:
> On Wed, 2014-07-16 at 11:23 +0200, Jakub Jelinek wrote:
> > On Wed, Jul 16, 2014 at 05:18:06AM -0400, David Edelsohn wrote:
> > > This seems weird. Why wasn't this file included before or whenever it
> > > was added for other *-linux target
Tobias Burnus wrote:
The problem is fixed by the attached patch. I will commit it as
obvious (to the trunk, i.e. GCC 5 alias GCC 4.10 only) once building
and regtesting has finished.
As I only saw later in Steve's email, it is a regression. Thus, I will
also apply it to the GCC 4.9 branch (wi
Hi,
N.M. Maclaren wrote:
On Jul 25 2014, Rezny, Mike wrote:
I am seeing the following problems in using the Fortran intrinsic
function, storage_size(), in gfortran version 4.9.0. 1: A calls to
this function is returning a 64-bit integer instead of a default
32-bit integer 2: the routine is
On Fri, Jul 25, 2014 at 9:50 AM, Martin Jambor wrote:
> Hi,
>
> parameter stmt of sra_modify_assign and sra_modify_constructor_assign
> is currently gimple*, although there is no need for the extra level of
> indirection and dereferencing. Thus this patch removes quite few
> stars and one ampersa
On Mon, 7 Jul 2014, Zhenqiang Chen wrote:
> The patch tries to search relative dir "../share/locale" from gcc.
> Although it can not cover all cases, I think it can cover most cases.
That's not how to use make_relative_prefix. You want e.g.
make_relative_prefix (argv[0], standard_bindir_prefix,
On Fri, 4 Jul 2014, Konstantin Serebryany wrote:
> BTW, I really want to change our current scheme of merging sanitizer
> sources to gcc --
> to use 'svn external' or some such instead of maintaining a copy.
I believe we should avoid all use of systems such as svn externals or git
submodules, so
> Jan Hubicka writes:
> >
> > I am lto bootstrapping/regtesting x86_64-linux and intend to comming once it
> > passes.
>
> You'll have to redo it with hstates, sorry, as it conflicts with my
> patchkit which I checked in earlier.
Hi,
this is vairant of patch I comitted.
Richard Biener
Hello,
Branch was rebased on trunk.
It contains fixes for several issues in the build system.
Now 'configure' can be called using relative path.
Also some options are now unnecessary, updated manual is posted
on wiki: https://gcc.gnu.org/wiki/Offloading in "How to try offloading enabled
GCC".
-
Hi,
parameter stmt of sra_modify_assign and sra_modify_constructor_assign
is currently gimple*, although there is no need for the extra level of
indirection and dereferencing. Thus this patch removes quite few
stars and one ampersand.
Bootstrapped and tested on x86_64-linux, OK for trunk?
Thank
On Fri, 25 Jul 2014, Jan-Benedict Glaw wrote:
> On Thu, 2014-07-24 16:30:13 -0400, Hans-Peter Nilsson
> wrote:
> > On Thu, 24 Jul 2014, Jan-Benedict Glaw wrote:
> > > On Tue, 2014-07-22 16:40:31 -0400, Hans-Peter Nilsson
> > > wrote:
> > > > Jan-Benedict, which host gcc version do you use when
OK, thanks!
Jason
On 07/24/2014 07:36 PM, Jan Hubicka wrote:
ipa-deivrt has code to do the tracking for you. All is needed is to cal
get_odr_type
for all polymorphic type that we care about. build_type_inheritance_graph just
walks all virtual methods to register all polymorphic types that matters (i.e.
have meth
Hi Cesar!
On Thu, 24 Jul 2014 15:44:13 -0700, Cesar Philippidis
wrote:
> On 07/24/2014 06:11 AM, Thomas Schwinge wrote:
> > I'd suggest to continue to handle all the data clauses [...]
>
> I moved all of the data clause matching back to gfc_match_omp_clauses,
> and I guarded the copyin clause w
> Jan Hubicka writes:
> >
> > I am lto bootstrapping/regtesting x86_64-linux and intend to comming once it
> > passes.
>
> You'll have to redo it with hstates, sorry, as it conflicts with my
> patchkit which I checked in earlier.
Yep I noticed that earlier and I am testing updated patch. I thin
Jan Hubicka writes:
>
> I am lto bootstrapping/regtesting x86_64-linux and intend to comming once it
> passes.
You'll have to redo it with hstates, sorry, as it conflicts with my
patchkit which I checked in earlier.
-Andi
--
a...@linux.intel.com -- Speaking for myself only
Committed to branch dmalcolm/jit:
gcc/jit/
* TODO.rst (error-checking): Remove various items that either
already were implemented, or are implemented by this commit.
* internal-api.h (gcc::jit::recording::type::is_numeric): New.
* libgccjit.c (RETURN_NULL_IF_FAIL_NO
How difficult would it be to make partial specializations work:
// Write n*pi once for every possible type
template
constexpr Tp npi = N * Tp(3.1415926535897932385L);
// Partial specialization for int type.
template
constexpr double npi = N * double(3.1415926535897932385L);
On Fri, Jul 25, 2014 at 1:35 PM, Richard Biener
wrote:
> On Thu, Jul 17, 2014 at 11:08 AM, Bin Cheng wrote:
>> Hi,
>> As quoted from the function difference_cannot_overflow_p,
>>
>> /* TODO: deeper inspection may be necessary to prove the equality. */
>> switch (code)
>> {
>> case PL
On Fri, Jul 25, 2014 at 1:27 PM, Richard Biener
wrote:
> On Thu, Jul 17, 2014 at 11:07 AM, Bin Cheng wrote:
>> Hi,
>> This is a series of three patches improving induction variable elimination.
>> Currently GCC only eliminates iv for very specific case when the loop's
>> latch could run zero time
Hi,
this patch make SCC hashes stronger by using DFS to get entry point independent
order. The DFS refactoring work is Richards, only hash_tree changes are mine
and I am responsible for all bugs :) Details are hopefully well documented in
hash_scc.
I tested the patch on Firefox and we manage to g
On Thu, Jul 17, 2014 at 11:08 AM, Bin Cheng wrote:
> Hi,
> As quoted from the function difference_cannot_overflow_p,
>
> /* TODO: deeper inspection may be necessary to prove the equality. */
> switch (code)
> {
> case PLUS_EXPR:
> return expr_equal_p (e1, offset) || expr_equal_p
Our x86_64 implementation it also checks whether frame pointer lies
within direct mapping zone (0x8800-c800), as
some frames are not in that zone and doesn't have shadow.
On Tue, Jul 22, 2014 at 2:43 PM, Andrey Ryabinin wrote:
> On 07/22/14 14:30, Yury Gribov wrote:
I
On Thu, Jul 17, 2014 at 11:07 AM, Bin Cheng wrote:
> Hi,
> This is a series of three patches improving induction variable elimination.
> Currently GCC only eliminates iv for very specific case when the loop’s
> latch could run zero times, i.e., when may_be_zero field of loop niter
> information ev
On Fri, Jul 25, 2014 at 2:11 AM, Andi Kleen wrote:
> This version addresses the review feedback. begin is gone now.
> add_flag is in the class. The changes in tree.c are nearer
> the original code now. Some other minor cleanups.
>
> Passed bootstrap and test and x86_64-linux. Ok to commit
> now?
On 07/24/2014 04:56 PM, Jason Merrill wrote:
+ /* Variable templates will need to have the class context. */
+ if (VAR_P (value))
+DECL_CONTEXT (value) = current_class_type;
Why isn't this covered by grokvardecl?
Oops, as the changelog indicated, this was to satisfy the old
On 25/07/2014 13:20, Roman Gareev wrote:
I have no idea. Is the Gimple basic block of S_3 never set, or is it set and
deleted on the way?
I think, that it is deleted on the way. I've found out, that the
Gimple basic block will be set, if we add the following code to the
generate_isl_schedule:
> I have no idea. Is the Gimple basic block of S_3 never set, or is it set and
> deleted on the way?
I think, that it is deleted on the way. I've found out, that the
Gimple basic block will be set, if we add the following code to the
generate_isl_schedule:
bb_schedule = isl_map_set_tuple_id (bb_s
2014-07-24 17:41 GMT+04:00 Jan Hubicka :
>> > So the patch is introducing yet another notion of clone (in addition to
>> > existing virtual clones
>> > and function versions used by ifun) and you add a new type of reference
>> > (CHKP) to link the
>> > original and the clone.
>> >
>> > Why do you
On Thu, 2014-07-24 16:30:13 -0400, Hans-Peter Nilsson wrote:
> On Thu, 24 Jul 2014, Jan-Benedict Glaw wrote:
> > On Tue, 2014-07-22 16:40:31 -0400, Hans-Peter Nilsson
> > wrote:
> > > Jan-Benedict, which host gcc version do you use when getting
> > > most targets to build with config-list.mk? M
On 07/24/2014 11:35 PM, Cary Coutant wrote:
>> It seems that the problem here is more general; a template argument list is
>> not in scope within that same template argument list. Can't we fix that
>> without special-casing conversion ops?
>
> I think conversion ops really are a special case.
T
On Mon, Jul 21, 2014 at 8:21 PM, Uros Bizjak wrote:
> Attached patch fixes libgo reflect test failure with libffi closures.
> The gccgo compiler started to use FFI closures recently; the compiler
> passes ffi_type_void for structures with zero members.
>
> ffi_call form src/alpha/ffi.c allows FFI
On 25 July 2014 04:50, Ed Smith-Rowland <3dw...@verizon.net> wrote:
> On 03/08/2014 01:33 PM, Jonathan Wakely wrote:
>>
>> On 8 March 2014 16:29, Ed Smith-Rowland wrote:
>>>
>>> On 03/08/2014 11:27 AM, Ed Smith-Rowland wrote:
The title says it all. This was just an oversight in the origi
Targets may not use the speed_p argument of MOVE_RATIO which makes
the function argument unused.
[should we fix the warning to account a macro argument use as use?]
Applied as obvious.
Richard.
2014-07-25 Richard Biener
* tree-inline.c (estimate_move_cost): Mark speed_p argument
61 matches
Mail list logo
