On Mon, Jan 05, 2015 at 10:39:03PM +0100, Jakub Jelinek wrote:
> > >http://gcc.gnu.org/ml/gcc-patches/2014-12/msg00297.html
> > > - -fsanitize=vptr support
> > How is this different from vtable pointer verification that we already
> > support? Is there some reason we can't just use that instead?
Two new directories are added in the project path, when gnatls is invoked
with --RTS=, just before the two directories for the target.
When the runtime is a single name, the directories are:
///lib/gnat
///share/gpr
Otherwise, the runtime directory is either an absolute path or a path
relative
Committed on trunk.
* gnatvsn.ads: Bump copyright year.
Index: gnatvsn.ads
===
--- gnatvsn.ads (revision 219191)
+++ gnatvsn.ads (working copy)
@@ -6,7 +6,7 @@
--
Jakub Jelinek writes:
> On Mon, Jan 05, 2015 at 10:40:37PM +0100, Jakub Jelinek wrote:
>> > Are there any doc updates that need to happen as a result of this patch?
>> > Patch itself is fine for the trunk, just want to make sure the doc side is
>> > good too.
>>
>> You're right, I'll add documen
When the target of a type conversion is an access to an interface type
and the operand is not an access type but a tagged object which covers
the target interface the frontend does not report an error. After this
patch the compiler reports the missing error:
package Speaker is
type Root is inte
This adds an additional warning message for Suppress (Elaboration_Check)
in SPARK mode:
The following is compiled with -gnatj55
1. pragma SPARK_Mode (On);
2. package SupEcheck is
3.pragma Suppress (Elaboration_Check);
|
>>> warning: Suppress
Hi Mike,
after some hours of sleep I realized that your step function can do something
very interesting,
(which you already requested previously):
That is: create a race condition that is _always_ at 100% missed by tsan:
cat lib.c
/* { dg-do compile } */
/* { dg-options "-O2 -fno-sanitize=all"
On some targets, the compiler does not generate a required divide by
zero check for the case of fixed-point operands. This was noticed in
the context of the second division function in Ada.Real_Time, but is
a quite general problem. The following program:
1. function DivCTest return Duration i
This fixes a problem in the diagnostic for violation of the restriction
No_Elaboration_Code_All. In some cases, the location of the restriction
incorrectly points to the pragma in system.ads. The following test should
compile as shown whether or not there is a NECA pragma in System.
1. pragma
On Tue, Jan 06, 2015 at 10:08:22AM +0100, Bernd Edlinger wrote:
> Hi Mike,
>
> after some hours of sleep I realized that your step function can do something
> very interesting,
> (which you already requested previously):
>
> That is: create a race condition that is _always_ at 100% missed by tsa
This is an internal change to create two new Boolean Name_Table
info fields. No external effect, no test.
Tested on x86_64-pc-linux-gnu, committed on trunk
2015-01-06 Robert Dewar
* exp_util.adb: Change name Name_Table_Boolean to
Name_Table_Boolean1.
* namet.adb: Chang
This patch implements a side effect of SPARK RM rule 7.1.3(11) which implies
that an effectively volatile formal parameter of mode out cannot be read.
-- Source --
-- async_writers_out.ads
package Async_Writers_Out with SPARK_Mode is
type Volat_Array is array (1 ..
An incomplete type may appear in the profile of a subprogram used in a
predicate for the type. Analysis of the constructed predicate function will
include a call to the subprogram, and an actual of the full type will be
resolved against an actual of the incomplete view. This patch handles this
cons
This adds an RM reference to J.2 for the run-time routines that allow
colon as a replacement for hash in based notation. Comment changes
only, no external effect, so no test.
Tested on x86_64-pc-linux-gnu, committed on trunk
2015-01-06 Robert Dewar
* s-valllu.adb, a-tiinau.adb, a-timo
The internal tree nodes for the standard Ada floating point types are
derived from back-end information provided via a type registration hook.
The registration is performed by the set_targ elaboration code, constructing
the FPT_Mode_Table which cstand.Create_Standard scans later on to construct
f
Enforce rule from E.2.3(14/3): the return type of an RCI function
must support external streaming; per 13.13.2(52/3) an anonymous access
type does not support external streaming.
The following code is illegal and must be rejected:
$ gcc -c rci_func_return_anon_access.adb
rci_func_return_anon_acce
Hello,
We should not enter the first iteration when length is 0. Testcase
attached. Difficult to reduce because register allocation generated
accidentally the correct return value.
testsuite OK
OK for 4.9 and trunk ?
Christian
2015-01-08 Christian Bruel
PR target/64507
* config/sh/sh
This change ensures that "and" and "or" operators affected by the
Short_Circuit_And_Or pragma are considered as part of SCO decisions,
just like the "and then" and "or else" operators.
The following compilation must produce a decision SCO as shown:
$ gcc -c -fdump-scos cc4.adb
$ grep ^CX cc4.ali
This checkin is preliminary work for a new restriction No_Use_Of_Entity.
No test needed, since no external effect yet!
Tested on x86_64-pc-linux-gnu, committed on trunk
2015-01-06 Robert Dewar
* namet.ads: Document use of Boolean2 for No_Use_Of_Entity.
* restrict.ads (No_Use_O
Ping.
Thank you,
Mantas M.
On 18/11/14 11:58, Richard Earnshaw wrote:
On 18/11/14 11:30, Mantas Mikaitis wrote:
Incorrect predefinitions for certain target architectures. E.g. arm7-m
does not contain NEON but the defintion __ARM_NEON_FP was switched on.
Similarly with armv6 and even armv2.
On Tue, 6 Jan 2015 10:16:33, Jakub Jelinek wrote:
>
> On Tue, Jan 06, 2015 at 10:08:22AM +0100, Bernd Edlinger wrote:
>> Hi Mike,
>>
>> after some hours of sleep I realized that your step function can do
>> something very interesting,
>> (which you already requested previously):
>>
>> That is: cr
Ping and changelog spaces removed.
Thank you,
Mantas M.
On 18/11/14 11:58, Richard Earnshaw wrote:
On 18/11/14 11:30, Mantas Mikaitis wrote:
Incorrect predefinitions for certain target architectures. E.g. arm7-m
does not contain NEON but the defintion __ARM_NEON_FP was switched on.
Similarly
On Tue, 2015-01-06 at 10:28 +0100, Christian Bruel wrote:
> Hello,
>
> We should not enter the first iteration when length is 0. Testcase
> attached. Difficult to reduce because register allocation generated
> accidentally the correct return value.
>
> testsuite OK
>
> OK for 4.9 and trunk ?
A new routine named __gnat_runtime_initialize is introduced to initialize
the runtime and another one to finalize it. Code from __gnat_finalize have
been moved to __gnat_runtime_initialize when it applies. This makes a C
main calling adainit() and adafinal() as documented behave as if the
main was
Jonathan Wakely writes:
> The powerpc64 ICE is fixed, so I'm committing the std::string ABI
> transition patch.
>
> This replaces our venerable Copy-on-Write std::string with a
> C++11-conforming* Small-String Optimized std::__cxx11::string.
>
> (* It's not quite 100% conforming, as it's missing
The Get routines in Text_IO that take a string argument were behaving
incorrectly when From'Last = Positive'Last. This is a very bizarre case
which probably will never occur in practice, but it leads to undefined
behavior (one possibility is a confusing raise of Data_Error). It is not
worth worryin
In the Alias_Atomic_Check block, Complain_CS has these lines:
if Known_Static_Esize (Ctyp) then
Error_Msg_N
("incorrect component size for "
& T & " components", Clause);
On 06/01/15 10:52 +0100, Rainer Orth wrote:
Unfortunately, this patch broke Solaris bootstrap with /bin/ld:
libstdc++.so fails to link with
ld: fatal: libstdc++-symbols.ver-sun: 5383: symbol
'std::locale::name[abi:cxx11]() const': symbol version conflict
l.5383 has
##_ZNKSt6locale4nameB5cx
Hi,
This patch updates the introduction to, and first section of, md.texi.
I was aiming to:
* Remove outdated details of the compiler.
* Remove long or obscure words that, while accurate, only served to
obfuscate a simple idea.
* Refer to similar things in a consistent fashion - in pa
Hi,
I was recently stuck on a flight and flicking through md.texi, when
I realised some of it was rather outdated. Consequently, I thought
I would have a go at updating it, and while I was there, clean up some
of the style issues I've spotted over the last few years.
I was aiming to:
* Remove
Hi,
This patch updates the second section of md.texi - "Everything about
Patterns".
I was aiming to:
* Remove outdated details of the compiler.
* Remove long or obscure words that, while accurate, only served to
obfuscate a simple idea.
* Refer to similar things in a consistent fashio
Hi,
This patch updates the text in the "Output Template" and "Output
Statement" sections of md.texi.
I was aiming to:
* Remove outdated details of the compiler.
* Remove long or obscure words that, while accurate, only served to
obfuscate a simple idea.
* Refer to similar things in a
Hi,
This patch updates the RTL Template section of md.texi.
I was aiming to:
* Remove outdated details of the compiler.
* Remove long or obscure words that, while accurate, only served to
obfuscate a simple idea.
* Refer to similar things in a consistent fashion - in particular
tr
Hi,
This patch updates the predicates section from md.texi.
I was aiming to:
* Remove outdated details of the compiler.
* Remove long or obscure words that, while accurate, only served to
obfuscate a simple idea.
* Refer to similar things in a consistent fashion - in particular
tr
OK to commit?
--
Eric BotcazouIndex: index.html
===
RCS file: /cvs/gcc/wwwdocs/htdocs/index.html,v
retrieving revision 1.946
diff -u -p -r1.946 index.html
--- index.html 23 Dec 2014 18:44:10 - 1.946
+++ index.html 6 Jan 2015 11:5
> I normally build with --disable-libsanitizer, because the sanitizers
> testresults are very unreproducable, so just annoying noise. This however
> makes most (all?) ubsan testcases fail, since they want to load a shared
> library that does not exist.
Same here, but I also have the problem with
On Tue, Jan 06, 2015 at 01:04:29PM +0100, Eric Botcazou wrote:
> > I normally build with --disable-libsanitizer, because the sanitizers
> > testresults are very unreproducable, so just annoying noise. This however
> > makes most (all?) ubsan testcases fail, since they want to load a shared
> > lib
Please use 'gen_cmpeqsi_t (len, const0_rtx)' for comparing a value
against zero instead of the bit test insn.
OK, also then OK to replace the other occurrences of the idiom for
coding consistency ? (not sure if I could commit this as obvious ?).
Cheers
Christian
2015-01-08 Christian B
> What errors do you get? Just curious.
Something along of "cannot load libtsan.so.0" and this comes from PR 58867.
> That said, I think your patch is fine.
Thanks, installed after testing on x86-64/Linux.
--
Eric Botcazou
Jonathan Wakely writes:
> Drat, I even tried to avoid that conflict, but apparently I thought
> the letter that comes after 'n' is 'n'!
>
> Does this fix it?
>
> --- a/libstdc++-v3/config/abi/pre/gnu.ver
> +++ b/libstdc++-v3/config/abi/pre/gnu.ver
> @@ -118,7 +118,7 @@ GLIBCXX_3.4 {
> # std::
Update the ZC constraint for MIPSR6 to allow it to be used as the memory
operand for implementations of atomic operations. Also switch the internal
implementation of atomic operations to use ZC instead of ZR.
This fix accurately describes the memory constraints for the LL and SC
instructions. An
This PR shows that the C FE accepts an invalid code, where
a flexible array member is being initialized with a string
constant, but the structure with the flexible array member
is in an array. GNU extension that allows initialization
of a flexible array members is a little bit of a gray area,
sinc
On 06/01/15 13:29 +0100, Rainer Orth wrote:
Jonathan Wakely writes:
Drat, I even tried to avoid that conflict, but apparently I thought
the letter that comes after 'n' is 'n'!
Does this fix it?
--- a/libstdc++-v3/config/abi/pre/gnu.ver
+++ b/libstdc++-v3/config/abi/pre/gnu.ver
@@ -118,7 +118
On Wed, Dec 17, 2014 at 03:28:15PM +0100, Richard Biener wrote:
> On Wed, 17 Dec 2014, Jakub Jelinek wrote:
>
> > Hi!
> >
> > MEM_REF (the only tcc_reference code with 2 operands) has TREE_READONLY set
> > whenever all the arguments are TREE_READONLY, which is wrong, if the
> > pointer/reference
Hi!
On Mon, Jan 05, 2015 at 10:31:17PM +0100, Jakub Jelinek wrote:
> Or you could e.g. do the
> if (HARD_FRAME_POINTER_IS_ARG_POINTER
> && !reload_completed
> && SIBLING_CALL_P (insn))
> { add_wild_read (bb_info); return; }
> case first, then compute const_call and memset_call,
>
On Tue, Jan 06, 2015 at 01:04:29PM +0100, Eric Botcazou wrote:
> > I normally build with --disable-libsanitizer, because the sanitizers
> > testresults are very unreproducable, so just annoying noise. This however
> > makes most (all?) ubsan testcases fail, since they want to load a shared
> > lib
On Tue, 6 Jan 2015, James Greenhalgh wrote:
> I was aiming to:
>
> * Remove outdated details of the compiler.
> * Remove long or obscure words that, while accurate, only served to
> obfuscate a simple idea.
> * Refer to similar things in a consistent fashion - in particular
> trying
Hi all,
here is a patch which adds an interface check for procedure pointer
components as acual arguments. Such a check is there already for
ordinary procedures and procedure pointers, but missing for PPCs. It
checks the interface of the actual argument versus the interface of
the dummy procedure,
Please add the following pair of patches to gcc 4.9. These two patches add
reflection support for ppc64 & ppc64le to gccgo in gcc 4.9, along with
a fix for recover that is needed once the reflection support is in
place. A bootstrap
build and testing was done on ppc64 & ppc64le.
Changes inc
On Tue, Jan 06, 2015 at 02:56:58PM +, Joseph Myers wrote:
> On Tue, 6 Jan 2015, James Greenhalgh wrote:
>
> > I was aiming to:
> >
> > * Remove outdated details of the compiler.
> > * Remove long or obscure words that, while accurate, only served to
> > obfuscate a simple idea.
> >
Add support for reflection for gccgo in gcc 4.9. This is not a backport
because reflection support in gcc trunk is done using FFI. Bootstrap
built and tested on ppc64, ppc64le.
2015-01-06Lynn Boger
* libgo/Makefile.am: Build the new files for libgo reflection
support on ppc64, ppc6
This is a backport to gcc 4.9 of the following change:
https://gcc.gnu.org/ml/gcc-patches/2014-10/msg00660.html. The original
patch had changes required for use with the FFI reflection support.
Since FFI is not used for reflection in gcc 4.9 those changes were omitted.
2015-01-06Lynn Bog
As requested, please find a paragraph-by-paragraph justification for
the changes in this patch below.
I hope this aids review.
Of particular interest for this patch is the removal of the text
describing the semicolon for a comment syntax. I believe that a
description of the syntax of a .md file d
On 1/6/2015 9:08 AM, Jakub Jelinek wrote:
@@ -2527,7 +2518,13 @@ scan_insn (bb_info_t bb_info, rtx_insn *
const_call ? "const" : "memset", INSN_UID (insn));
/* See the head comment of the frame_read field. */
- if (reload_completed)
+ if (reload_comp
Martin,
> I suppose that could be done by something like the following, which I
> have tested only very mildly so far, in particular I have not double
> checked that get_inner_reference is cfun-agnostic.
The patch introduces no regressions on x86-64/Linux and makes the testcase
(gnat.dg/specs/pa
On Tue, 6 Jan 2015, James Greenhalgh wrote:
On Tue, Jan 06, 2015 at 02:56:58PM +, Joseph Myers wrote:
On Tue, 6 Jan 2015, James Greenhalgh wrote:
I was aiming to:
* Remove outdated details of the compiler.
* Remove long or obscure words that, while accurate, only served to
obfusc
> Date: Tue, 6 Jan 2015 10:16:33 +0100
> From: ja...@redhat.com
> To: bernd.edlin...@hotmail.de
> CC: mikest...@comcast.net; hjl.to...@gmail.com; gcc-patches@gcc.gnu.org;
> dvyu...@google.com
> Subject: Re: [PATCH] Fix sporadic failure in
> g++.dg/tsan/a
Hello.
There's suggested patch for PR ipa/64503 that was tested on x86_64 and it works.
I would like to ask Uros to test it on an aplha machine before we install the
patch.
Thanks,
Martin
>From d4738c61467e53d04b295cfc029ab89707ac29ce Mon Sep 17 00:00:00 2001
From: mliska
Date: Tue, 6 Jan 2015
On Tue, Jan 6, 2015 at 6:49 PM, Martin Liška wrote:
> Hello.
>
> There's suggested patch for PR ipa/64503 that was tested on x86_64 and it
> works.
> I would like to ask Uros to test it on an aplha machine before we install
> the patch.
Yes, this works for me on all IPA tests that were failing pr
On Tue, 6 Jan 2015, Mikhail Maltsev wrote:
> Hi, all!
> I'm pinging about this patch:
> https://gcc.gnu.org/ml/gcc-patches/2014-12/msg01925.html (PR c/48956)
> I know that maybe it's too early for sending a ping (less than 2
> weeks), but I also have a question regarding my patch:
> Is this patch
On 01/05/15 16:15, Eric Botcazou wrote:
Hi,
the attached patch removes obsolete ports (c4x, m68hc11 and ms1), toggles the
'p' letter and adjust accordingly (only avr, fr30, m68k, mcore, rs6000 and sh
still use define_peephole) and removes trailing spaces.
OK to commit?
Some ports are missing (
On Tue, 6 Jan 2015, Marek Polacek wrote:
> 2015-01-06 Marek Polacek
>
> PR c/64417
> c/
> * c-typeck.c (process_init_element): Disallow initialization of
> a flexible array member with a string constant if the structure
> is in an array.
> testsuite/
> * gcc.c-tor
On Tue, 6 Jan 2015, James Greenhalgh wrote:
> > and "Update text." is thoroughly unhelpful as a ChangeLog entry to
> > explain the intent of the changes.
>
> Well, indeed, but ChangeLog entries have always been a
> thoroughly unhelpful "what changed" rather than "why did it
> change". (grep ": U
Sorry, hold off on this one for now. I missed the update to
libgo/go/reflect/all_test.go for ppc64 and ppc64le in this patch and
when changed to actually test these goarch values it is failing.
On 01/06/2015 09:37 AM, Lynn A. Boger wrote:
Add support for reflection for gccgo in gcc 4.9. This
On Tue, 6 Jan 2015, James Greenhalgh wrote:
> > -The @file{.md} file for a target machine contains a pattern for each
> > -instruction that the target machine supports (or at least each instruction
> > -that is worth telling the compiler about). It may also contain comments.
> > -A semicolon caus
Currently the C FE's -Wdiv-by-zero warns only for INTEGER_CSTs,
unlike C++, which can also handle const ints (yes, different
constant expression rules). But since it's easy to warn for
consts in the C FE as well, and we already warn for shifts
with const ints, I think we can go with the following.
This patch by Chris Manghane skips initializing zero-sized fields in
constructor expressions. Initializing them tends to lead into GIMPLE
errors when using map composite literals. Note that zero-sized fields
are useful in maps, but of course the compiler should not crash. This
is http://golang.o
On Tue, 6 Jan 2015, Marek Polacek wrote:
> Currently the C FE's -Wdiv-by-zero warns only for INTEGER_CSTs,
> unlike C++, which can also handle const ints (yes, different
> constant expression rules). But since it's easy to warn for
> consts in the C FE as well, and we already warn for shifts
> wi
On Tue, Jan 06, 2015 at 12:07:17PM -0500, John David Anglin wrote:
> On 1/6/2015 9:08 AM, Jakub Jelinek wrote:
> >@@ -2527,7 +2518,13 @@ scan_insn (bb_info_t bb_info, rtx_insn *
> > const_call ? "const" : "memset", INSN_UID (insn));
> > /* See the head comment of the frame_re
On Mon, Jan 05, 2015 at 09:31:52PM -0600, Segher Boessenkool wrote:
> On Mon, Jan 05, 2015 at 07:50:33PM -0500, Michael Meissner wrote:
> > This patch fixes PR 64505, which is an issue that one of the users of the
> > Advance Toolchain found where -m32 -mpowerpc64 generated an insn not found
> > me
On 01/06/15 04:57, Eric Botcazou wrote:
OK to commit?
-- Eric Botcazou
p.diff
Index: index.html
===
RCS file: /cvs/gcc/wwwdocs/htdocs/index.html,v
retrieving revision 1.946
diff -u -p -r1.946 index.html
--- index.html 23 Dec 20
As discussed in previous threads, we need to get rid of
deferred_asm_name (and limbo nodes, etc) as part of the debug-early work.
The original patch for deferred_asm_name came in Alex's patch here:
https://gcc.gnu.org/ml/gcc-patches/2009-06/msg00030.html
One alternative to avoid this mechanism
On Mon, Jan 5, 2015 at 7:50 PM, Michael Meissner
wrote:
> This patch fixes PR 64505, which is an issue that one of the users of the
> Advance Toolchain found where -m32 -mpowerpc64 generated an insn not found
> message in some cases. I traced this down to rs6000_secondary_reload
> generating a re
On Jan 6, 2015, at 9:45 AM, Bernd Edlinger wrote:
> I tried your suggestion now, and it seems to work. (on a 4-way core AMD64
> laptop)
>
> Would you prefer this over adding a sleep in Thread1, which I posted
> previously?
The problem with the patch is there is nothing in the patch that makes
On 01/05/2015 04:15 PM, Eric Botcazou wrote:
Hi,
the attached patch removes obsolete ports (c4x, m68hc11 and ms1), toggles the
'p' letter and adjust accordingly (only avr, fr30, m68k, mcore, rs6000 and sh
still use define_peephole) and removes trailing spaces.
OK to commit?
Some ports are miss
On Wed, Nov 5, 2014 at 12:25 AM, Zhenqiang Chen wrote:
> The patch leads to big regression for float operators on target without hard
> fpu support due to register shuffle.
>
> Please refer https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63743 for more
> detail.
>
> Thanks!
> -Zhenqiang
>
>> -Ori
On Jan 5, 2015, at 5:06 PM, Bernd Edlinger wrote:
>
> I tried to elaborate your idea a bit, and used proper atomics.
> It is necessary that the logic of the step function is completely invisible
> to tsan.
> Therefore it should not call sleep,
Again, sleep can’t fix race conditions, so therefo
In this testcase the compiler is confused by the local class and thinks
that the lambda is in the context of the enclosing function. Fixed by
recognizing when a lambda is directly within a local class.
Tested x86_64-pc-linux-gnu, applying to trunk.
commit f5ba54d8bcbd15d6d9519b0140a5e430e9822d
The existing code was assuming that offsetof will always be fully
instantiated if it goes through tsubst at all. In general this is an
invalid assumption; we need to deal with partial instantiation in
still-dependent context.
Tested x86_64-pc-linux-gnu, applying to trunk.
commit fbbb80c79e464
We were complaining about IsType not being constant, but we shouldn't
think about it having a constant value or not, because it is
type-dependent; a variable template can have a specialization with a
different type.
Tested x86_64-pc-linux-gnu, applying to trunk.
commit dff5042c89e83955238c9ec5
On 01/06/2015 05:01 PM, Jason Merrill wrote:
We were complaining about IsType not being constant, but we shouldn't
think about it having a constant value or not, because it is
type-dependent; a variable template can have a specialization with a
different type.
The second patch fixes a diagnosti
Let's also run the testsuite with the environment variable
GCC_COMPARE_DEBUG=1.
Jason
> I might claim updating this shouldn't ever require a review :-)
OK, it was mainly about toggling the 'p' letter...
I have installed the attached patch for lm32 (based on info privately provided
by Sébastien) and visium.
--
Eric BotcazouIndex: backends.html
===
> I think that for nios2 the correct entry is probably "SCpd", but the
> descriptions of some of the things in the table are too terse for me to
> be 100% sure that's correct. E.g., the nios2 architecture doesn't
> include the concept of "condition codes" at all, so how many registers
> they might
On Tue, 6 Jan 2015 11:47:30, Mike Stump wrote:
>
> On Jan 6, 2015, at 9:45 AM, Bernd Edlinger wrote:
>> I tried your suggestion now, and it seems to work. (on a 4-way core AMD64
>> laptop)
>>
>> Would you prefer this over adding a sleep in Thread1, which I posted
>> previously?
>
> The problem
I've committed a patch to libgo to add the sources for three standard
Go tools: go, cgo, and gofmt. The go tool is used by most Go
programmers to build, test, and install Go programs, as well as to
fetch Go code from the Internet. It more or less replaces make. The
cgo tool is invoked by the go
> Some ports are missing (lm32, moxie, nios2, nvptx, rl78, rx) so the relevant
> maintainers are CCed (see 6.3.9 Anatomy of a Target Back End in the doc).
The page is directly browsable at https://gcc.gnu.org/backends.html
For the moxie, nvptx, rl178 and rx ports, maintainers can send me the stri
Hi Eric,
On Wed, Jan 7, 2015 at 2:39 AM, Eric Botcazou wrote:
> The page is directly browsable at https://gcc.gnu.org/backends.html
>
> For the moxie, nvptx, rl178 and rx ports, maintainers can send me the string
> as Sandra did for the nios2 port and I'll update the document.
Xtensa is now supp
This patch by Chris Manghane fixes the export data for complex
constants with a zero imaginary part. This is
https://code.google.com/p/gofrontend/issues/detail?id=31 .
Bootstrapped and ran Go testsuite on x86_64-unknown-linux-gnu.
Committed to mainline.
Ian
diff -r fd1c78fac62c go/expressions.cc
On Jan 6, 2015, at 3:22 PM, Bernd Edlinger wrote:
> Yes, I think too that it can't fail under these conditions.
If you mean your version… A lot has been written on how to to make racy code
non-racy… I’d refer you to the literature on all the various solutions people
have found to date. I don
Quite some time ago (r184879) I reformatted the entry for the i386
-mrecip= option as part of a general cleanup of that section. Here's
the corresponding change for the very similary RS/6000 option, which
I've committed as an "obvious fix".
-Sandra
2015-01-06 Sandra Loosemore
gc
On 2015-01-05 8:40 PM, Bin.Cheng wrote:
On Tue, Jan 6, 2015 at 7:36 AM, Vladimir Makarov wrote:
On 2015-01-05 12:31 PM, Jeff Law wrote:
On 01/05/15 00:44, Kito Cheng wrote:
Hi Vladimir:
This patch has a discusses with you in May 2014, this patch is about
the caller-save register store an
Bootstrapped and tested. It could be also patched to 4.9 branch.
Thanks!
--
Regards,
Tim Shen
commit dfe3a26759893849020a659b14fafe8b27e90dae
Author: timshen
Date: Tue Jan 6 19:30:27 2015 -0800
PR libstdc++/64239
* include/bits/regex.h (match_results<>::swap): Use std::
On Tue, 6 Jan 2015 16:32:35, Mike Stump wrote:
>
> On Jan 6, 2015, at 3:22 PM, Bernd Edlinger wrote:
>> Yes, I think too that it can't fail under these conditions.
>
> If you mean your version… A lot has been written on how to to make racy code
> non-racy… I’d refer you to the literature on all
94 matches
Mail list logo