Ping?
-Original Message-
From: Tony Wang [mailto:tony.w...@arm.com]
Sent: Thursday, August 21, 2014 2:15 PM
To: 'gcc-patches@gcc.gnu.org'
Subject: [PATCH 1/3,ARM,libgcc]Code size optimization for the fmul/fdiv and
dmul/ddiv function in libgcc
Hi there,
In libgcc the file
Ping?
-Original Message-
From: Tony Wang [mailto:tony.w...@arm.com]
Sent: Thursday, August 21, 2014 2:15 PM
To: 'gcc-patches@gcc.gnu.org'
Subject: [PATCH 2/3,ARM,libgcc]Code size optimization for the fmul/fdiv and
dmul/ddiv function in libgcc
Step 2: Mark all the symbols around
Ping?
-Original Message-
From: Tony Wang [mailto:tony.w...@arm.com]
Sent: Thursday, August 21, 2014 2:15 PM
To: 'gcc-patches@gcc.gnu.org'
Subject: [PATCH 3/3,ARM,libgcc]Code size optimization for the fmul/fdiv and
dmul/ddiv function in libgcc
Step 3: Test cases to verify the
This patch is based on 1/2 and 2/2 on the series. When the patch is
approved, OpenCoarrays needs to be adapted; however, as surplus
arguments of the callee are ignored, no immediate action is required.
(And some delay avoids issues with compilers being older than the library.)
The issue comes
On Thu, 28 Aug 2014, Kugan wrote:
On 27/08/14 23:02, Kugan wrote:
On 27/08/14 20:01, Uros Bizjak wrote:
Hello!
2014-08-07 Kugan Vivekanandarajah kug...@linaro.org
* calls.c (precompute_arguments): Check
promoted_for_signed_and_unsigned_p and set the promoted mode.
Hello,
This patch adds support for SI/DO masked interleaves.
Bootstrapped.
AVX-512* tests on top of patch-set all pass
under simulator.
Is it ok for trunk?
gcc/
* config/i386/sse.md
(define_insn avx2_interleave_highv4dimask_name): Add masking.
(define_insn
On 28/08/14 16:44, Marc Glisse wrote:
On Thu, 28 Aug 2014, Kugan wrote:
On 27/08/14 23:02, Kugan wrote:
On 27/08/14 20:01, Uros Bizjak wrote:
Hello!
2014-08-07 Kugan Vivekanandarajah kug...@linaro.org
* calls.c (precompute_arguments): Check
promoted_for_signed_and_unsigned_p and set
Ping. Add Joseph S. Myers as driver maintainer.
-Maxim
Original Message
Subject:Fwd: [PATCH] Add patch for debugging compiler ICEs.
Date: Tue, 19 Aug 2014 17:57:51 +0400
From: Maxim Ostapenko m.ostape...@partner.samsung.com
To: Jeff Law l...@redhat.com, GCC
On 27/08/14 20:07, Richard Biener wrote:
On Wed, Aug 27, 2014 at 12:01 PM, Uros Bizjak ubiz...@gmail.com wrote:
Hello!
2014-08-07 Kugan Vivekanandarajah kug...@linaro.org
* calls.c (precompute_arguments): Check
promoted_for_signed_and_unsigned_p and set the promoted mode.
On Thu, Aug 28, 2014 at 9:05 AM, Kirill Yukhin kirill.yuk...@gmail.com wrote:
Hello,
This patch adds support for SI/DO masked interleaves.
Bootstrapped.
AVX-512* tests on top of patch-set all pass
under simulator.
Is it ok for trunk?
gcc/
* config/i386/sse.md
On Wed, Aug 27, 2014 at 3:45 PM, Andi Kleen a...@firstfloor.org wrote:
Andi Kleen a...@firstfloor.org writes:
PING!
Andi Kleen a...@firstfloor.org writes:
PING^2 !
Would be nice to make slim bootstrap work, it really speeds it up quite
a bit.
From: Andi Kleen a...@linux.intel.com
To
2014-08-28 0:19 GMT+04:00 Vladimir Makarov vmaka...@redhat.com:
On 2014-08-26 5:42 PM, Ilya Enkovich wrote:
Hi,
Here is a patch I tried. I apply it over revision 214215. Unfortunately
I do not have a small reproducer but the problem can be easily reproduced on
SPEC2000 benchmark 175.vpr.
The following fixes a few ICEs and C++ testsuite fails.
Bootstrapped and tested on x86_64-unknown-linux-gnu, applied.
Richard.
2014-08-28 Richard Biener rguent...@suse.de
* match-constant-folding.pd (x + 0 - x): Wrap result in
a NON_LVALUE_EXPR to account for the C++
2014-08-28 1:39 GMT+04:00 Jeff Law l...@redhat.com:
On 08/26/14 15:42, Ilya Enkovich wrote:
diff --git a/gcc/calls.c b/gcc/calls.c
index 4285ec1..85dae6b 100644
--- a/gcc/calls.c
+++ b/gcc/calls.c
@@ -1122,6 +1122,14 @@ initialize_argument_information (int num_actuals
ATTRIBUTE_UNUSED,
On Wed, Aug 27, 2014 at 4:42 PM, Kito Cheng kito.ch...@gmail.com wrote:
Hi all:
This patch basically is extension for r210100[1], stream out
non-explicit -fno-tree-loop-distribute-patterns since compile with
`-flto -O3 -fno-builtin` still may gen builtin function call during
LTO phase.
LTO
On Thu, Aug 28, 2014 at 9:50 AM, Kugan
kugan.vivekanandara...@linaro.org wrote:
On 27/08/14 20:07, Richard Biener wrote:
On Wed, Aug 27, 2014 at 12:01 PM, Uros Bizjak ubiz...@gmail.com wrote:
Hello!
2014-08-07 Kugan Vivekanandarajah kug...@linaro.org
* calls.c (precompute_arguments):
Hi Richard:
I think preserve -fno-builtin is better than
-fno-tree-loop-distribute-patterns too,
However if we preserve -fno-builtin, the coming problem is should we
preserve all -fbuiltin-* and do the check logic[1] in common code in
gcc?
btw, in our internal gcc 4.9.x tree is move
On Thu, 28 Aug 2014, Kito Cheng wrote:
Hi Richard:
I think preserve -fno-builtin is better than
-fno-tree-loop-distribute-patterns too,
However if we preserve -fno-builtin, the coming problem is should we
preserve all -fbuiltin-* and do the check logic[1] in common code in
gcc?
No,
This merges from trunk the fold_stmt re-org changes so I can
go forward with some builtin simplification stuff.
Committed.
Richard.
2014-08-28 Richard Biener rguent...@suse.de
Merge from trunk r214266 through r214675.
Hi all:
-fno-builtin is seem not only for the c family front-end, but also
used in LTO now, so move it to common.opt and change it to `Common`.
From 47552b58a09ac9d944be1c35bb5c938f4cb8ec0f Mon Sep 17 00:00:00 2001
From: Kito Cheng k...@andestech.com
Date: Thu, 14 Aug 2014 11:34:26 +0800
Subject:
Hi all:
The purpose for this patch is prevent `-flto -O3 -fno-builtin` gen
builtin function,
so checking -fno-builit, and then disable
-ftree-loop-distribute-patterns if if -fno-builit enabled, the prev
discuss in [1], and this patch dependence on [2].
[1]
Hi Richard:
thanks you comment :)
I send new patch for move -fno-builtin to common.opt and check it in
lto-lang.c (lto_post_options).
https://gcc.gnu.org/ml/gcc-patches/2014-08/msg02555.html
https://gcc.gnu.org/ml/gcc-patches/2014-08/msg02556.html
On Thu, Aug 28, 2014 at 5:29 PM, Richard Biener
On Thu, 28 Aug 2014, Kito Cheng wrote:
Hi all:
-fno-builtin is seem not only for the c family front-end, but also
used in LTO now, so move it to common.opt and change it to `Common`.
Please leave it in c-family and just add LTO to the set of supported
languages. -fno-builtin isn't
This patch contains a port of VTV -fvtable-verify=std for Cygwin and MinGW.
Since weak symbols on Windows and Linux are implemented differently, and
VTV should have the possibility to be switched on and off, the structure
of the feature had to be modified.
On Linux libstdc++ contains the weak
On 26/08/14 14:37, Jiong Wang wrote:
thanks,
verified no regression on aarch64-none-elf bare-metal check-gcc/check-gdb.
-- Jiong
On 22/08/14 23:05, Richard Henderson wrote:
Delay cfi restore opcodes until the stack frame is deallocated.
This reduces the number of cfi advance opcodes
On Thu, Aug 28, 2014 at 10:37 AM, Ilya Enkovich enkovich@gmail.com wrote:
2014-08-28 1:39 GMT+04:00 Jeff Law l...@redhat.com:
On 08/26/14 15:42, Ilya Enkovich wrote:
diff --git a/gcc/calls.c b/gcc/calls.c
index 4285ec1..85dae6b 100644
--- a/gcc/calls.c
+++ b/gcc/calls.c
@@ -1122,6
2014-08-28 16:42 GMT+04:00 Uros Bizjak ubiz...@gmail.com:
On Thu, Aug 28, 2014 at 10:37 AM, Ilya Enkovich enkovich@gmail.com
wrote:
2014-08-28 1:39 GMT+04:00 Jeff Law l...@redhat.com:
On 08/26/14 15:42, Ilya Enkovich wrote:
diff --git a/gcc/calls.c b/gcc/calls.c
index 4285ec1..85dae6b
On Fri, Aug 22, 2014 at 2:21 PM, Ilya Enkovich enkovich@gmail.com wrote:
Hi,
On Cauldron 2014 we had a couple of talks about relaxation of ebx usage in
32bit PIC mode. It was decided that the best approach would be to not fix
ebx register, use speudo register for GOT base address and
The following fixes two testcases in PR62283 which are not
vectorized because they are deemed not profitable to. They
are in fact not if we employ peeling for alignment but they
are (according to the cost model and my naiive thinking) if
we do not do that.
And it's trivial to see that peeling a
On Thu, Aug 28, 2014 at 2:54 PM, Ilya Enkovich enkovich@gmail.com wrote:
diff --git a/gcc/calls.c b/gcc/calls.c
index 4285ec1..85dae6b 100644
--- a/gcc/calls.c
+++ b/gcc/calls.c
@@ -1122,6 +1122,14 @@ initialize_argument_information (int num_actuals
ATTRIBUTE_UNUSED,
2014-08-28 17:01 GMT+04:00 Uros Bizjak ubiz...@gmail.com:
On Fri, Aug 22, 2014 at 2:21 PM, Ilya Enkovich enkovich@gmail.com wrote:
Hi,
On Cauldron 2014 we had a couple of talks about relaxation of ebx usage in
32bit PIC mode. It was decided that the best approach would be to not fix
Hello,
This patch introduces AVX-512 narrowing moves.
Bootstrapped.
AVX-512* tests on top of patch-set all pass
under simulator.
Is it ok for trunk?
gcc/
* config/i386/i386-modes.def: Add V12QI, V14QI, V6HI modes.
* config/i386/sse.md
(define_mode_iterator
On 08/27/2014 03:40 PM, Jason Merrill wrote:
OK.
Jason
Is this OK for 4.9 also?
It builds and tests clean on x86_64-linux.
Attached slightly modified patch.
Ed
libcpp/
2014-08-28 Edward Smith-Rowland 3dw...@verizon.net
PR cpp/23827 - standard C++ should not have hex float
2014-08-28 17:08 GMT+04:00 Uros Bizjak ubiz...@gmail.com:
On Thu, Aug 28, 2014 at 2:54 PM, Ilya Enkovich enkovich@gmail.com wrote:
diff --git a/gcc/calls.c b/gcc/calls.c
index 4285ec1..85dae6b 100644
--- a/gcc/calls.c
+++ b/gcc/calls.c
@@ -1122,6 +1122,14 @@
This tries to prevent NON_LVALUE_EXPR from leaking in to GIMPLE
(happens on trunk also, but mostly savaged by re-gimplifying
GENERIC folding results which strips them). We need a better
solution in the end (fix the C++ frontend), but for now the
following should fix things enough. (fingers
On Thu, 28 Aug 2014, Ed Smith-Rowland wrote:
Is this OK for 4.9 also?
It builds and tests clean on x86_64-linux.
Attached slightly modified patch.
In my opinion it is not appropriate for a backport, no. If someone was
using hex floats with -std=c++98 with 4.9.1, it should still work with
On 08/28/2014 09:41 AM, Marc Glisse wrote:
In my opinion it is not appropriate for a backport, no. If someone was
using hex floats with -std=c++98 with 4.9.1, it should still work with
4.9.2, I only expect to have to fix such things when moving to 5.0.
Agreed.
Jason
Hello,
This patch adds patterns to support FMA new insns.
Bootstrapped.
AVX-512* tests on top of patch-set all pass
under simulator.
Is it ok for trunk?
gcc/
* config/i386/sse.md
(define_mode_iterator VF_AVX512VL): New.
(define_mode_iterator FMAMODEM): Allow 128/256bit
Now as the fold_stmt re-org is merged from trunk this moves the
simplify dispatch first before doing the legacy stuff. It also
adds dumping to this place and removes dumping from
tree-ssa-forwprop.c (as there it catches all fold_stmt transforms
done). I now also dump the associated sequence
On Wed, Aug 27, 2014 at 4:42 AM, Aldy Hernandez al...@redhat.com wrote:
This patch fixes a bunch of guality failures. With it I get 144 guality.exp
failures vs. 163 for make check-gcc RUNTESTFLAGS=guality.exp. A lot
better than 100% fail rate ;-).
Variable DIEs were not being reused.
On 28/08/14 13:36, Jiong Wang wrote:
I am curious about why dwarf2out_frame_debug_expr only handle
PRE/POST_MODIFY on dest
while no handling on src ?
for example the following rule:
(set reg (mem_post_modify sp offset))
Probably because dwarf2out was originally written to handle just
On 08/28/2014 09:47 AM, Jason Merrill wrote:
On 08/28/2014 09:41 AM, Marc Glisse wrote:
In my opinion it is not appropriate for a backport, no. If someone was
using hex floats with -std=c++98 with 4.9.1, it should still work with
4.9.2, I only expect to have to fix such things when moving to
On 08/22/2014 10:39 PM, Mike Stump wrote:
On Aug 22, 2014, at 5:18 AM, Bernd Schmidt ber...@codesourcery.com wrote:
Here's another attempt.
Ok?
Ok. Thanks a ton for doing the work.
The next question would be what to do with gcc.c-torture/unsorted. As
far as I can tell, these are all
The tests for the non-standard distributions have bogus standard
references. [rand.concept.dist] comes from an old C++0x draft, and the
[rand.dist.ext.*] labels are entirely fictional because obviously
non-standard extensions are not in the standard.
Tested x86_64-linux, committed to trunk.
Hi Richard:
-fno-builtin is seem not only for the c family front-end, but also
used in LTO now, so move it to common.opt and change it to `Common`.
Please leave it in c-family and just add LTO to the set of supported
languages. -fno-builtin isn't meaningful for other frontends
and we just
Applied
On Thu, Aug 28, 2014 at 3:29 PM, Ilya Enkovich enkovich@gmail.com wrote:
diff --git a/gcc/calls.c b/gcc/calls.c
index 4285ec1..85dae6b 100644
--- a/gcc/calls.c
+++ b/gcc/calls.c
@@ -1122,6 +1122,14 @@ initialize_argument_information (int num_actuals
ATTRIBUTE_UNUSED,
On Wed, Aug 27, 2014 at 7:11 PM, Tom Tromey t...@tromey.com wrote:
Siva My patch is still using a single function to register libstdc++
Siva xmethods. Do you mean there should be a single function for pretty
Siva printers and xmethods together?
Yeah, that's my view.
I am probably not
On 08/26/2014 10:15 AM, David Malcolm wrote:
Attached is a revised version of #225, with the following changes:
* fix for the above: avoid introducing a new shadow name note within
force_nonfallthru_and_redirect by introducing a new local rtx_insn *
new_head and renaming note to it in the
Richard Biener wrote:
On Mon, Aug 25, 2014 at 11:07 PM, Sebastian Pop seb...@gmail.com wrote:
Sebastian Pop wrote:
Richard Biener wrote:
I think it would be better to identify a set of features we rely on that
are not present in earlier versions and make the test a link
test
On 08/26/2014 05:58 AM, Jiong Wang wrote:
On 22/08/14 23:05, Richard Henderson wrote:
Don't continually re-read data from cfun-machine.
* config/aarch64/aarch64.c (aarch64_expand_prologue): Load
cfun-machine-frame.hard_fp_offset into a local variable.
---
On 28/08/14 17:48, Richard Henderson wrote:
On 08/26/2014 05:58 AM, Jiong Wang wrote:
there is a field hardfp_offset in aarch64_frame, and I think that field is
not used and not initialized correctly.
how about hoisting the calculation to aarch64_layout_frame to avoid duplicated
calcuation
Bin.Cheng wrote:
Is the interface between isl/gcc stable enough? If it's not, the work
compatible is definitely confusing for users who don't know isl like
me. If it is stable, it won't be a problem.
The required version of ISL is documented in GCC's doc/install.texi:
@item ISL Library
Siva == Siva Chandra sivachan...@google.com writes:
Tom Yeah, that's my view.
Siva I am probably not understanding it right again.
It's ok. I am having some trouble myself.
Siva Are you suggesting that in hook.in, we just have single function
Siva call like this:
Siva register_python_hooks
On Tue, Aug 26, 2014 at 7:52 PM, Bill Schmidt
wschm...@linux.vnet.ibm.com wrote:
Hi,
This patch adds a few more cases of overloaded vector built-ins to
support V2DI and V2DF modes: vec_xl, vec_xst, vec_splat, vec_div,
vec_mul, vec_round. These are all straightforward. For vec_div and
On 08/28/14 06:58, Richard Biener wrote:
On Wed, Aug 27, 2014 at 4:42 AM, Aldy Hernandez al...@redhat.com wrote:
This patch fixes a bunch of guality failures. With it I get 144 guality.exp
failures vs. 163 for make check-gcc RUNTESTFLAGS=guality.exp. A lot
better than 100% fail rate ;-).
On 08/25/2014 11:53 PM, Aldy Hernandez wrote:
My current predicament is that dwarf2out_early_decl() is called early
enough such that dwarf2out_decl() sets the context die to the entire
compilation unit. Which means, that local variables end up with global
scope. I was thinking of hacking
On 08/28/2014 01:34 PM, Aldy Hernandez wrote:
I wonder if instead of early dumping of all the DECLs, we could only
dump the toplevel scoped DECLs, and let inheritance set the proper
contexts.
Yes, I think this makes a lot more sense; do it at a well-defined point
in compilation rather than as
On 08/28/2014 03:01 PM, Uros Bizjak wrote:
I'd like to avoid X86_TUNE_RELAX_PIC_REG and always treat EBX as an
allocatable register. This way, we can avoid all mess with implicit
xchgs in atomic_compare_and_swapdwi_doubleword. Also, having
allocatable EBX would allow us to introduce
On Thu, Aug 28, 2014 at 3:15 PM, Kirill Yukhin kirill.yuk...@gmail.com wrote:
Hello,
This patch introduces AVX-512 narrowing moves.
Bootstrapped.
AVX-512* tests on top of patch-set all pass
under simulator.
Is it ok for trunk?
gcc/
* config/i386/i386-modes.def: Add V12QI, V14QI,
On Thu, Aug 28, 2014 at 3:15 PM, Kirill Yukhin kirill.yuk...@gmail.com wrote:
Hello,
This patch introduces AVX-512 narrowing moves.
Bootstrapped.
AVX-512* tests on top of patch-set all pass
under simulator.
Is it ok for trunk?
gcc/
* config/i386/i386-modes.def: Add V12QI, V14QI,
On Thu, Aug 28, 2014 at 3:48 PM, Kirill Yukhin kirill.yuk...@gmail.com wrote:
Hello,
This patch adds patterns to support FMA new insns.
Bootstrapped.
AVX-512* tests on top of patch-set all pass
under simulator.
Is it ok for trunk?
gcc/
* config/i386/sse.md
On Thu, Aug 28, 2014 at 10:15 AM, Tom Tromey t...@tromey.com wrote:
Siva Are you suggesting that in hook.in, we just have single function
Siva call like this:
Siva register_python_hooks (gdb.current_objfile ())
Siva and, this function register_python_hooks lives somewhere else and
Siva calls
Hi,
I stumbled over the problem, that on win32 c++11's Thread support is
broken. I found a patch from Tomohiro Kashiwada, who did a great job.
Only he didn't pursue to have it integrated since more than two years.
I have applied his patch and fixed some compiler warnings and obvious
On Fri, Aug 22, 2014 at 2:21 PM, Ilya Enkovich enkovich@gmail.com wrote:
On Cauldron 2014 we had a couple of talks about relaxation of ebx usage in
32bit PIC mode. It was decided that the best approach would be to not fix
ebx register, use speudo register for GOT base address and let
On August 28, 2014 8:01:05 PM CEST, Jason Merrill ja...@redhat.com wrote:
On 08/28/2014 01:34 PM, Aldy Hernandez wrote:
I wonder if instead of early dumping of all the DECLs, we could only
dump the toplevel scoped DECLs, and let inheritance set the proper
contexts.
Yes, I think this makes a
Thanks!
On 8/28/14, Jonathan Wakely jwak...@redhat.com wrote:
Applied
On 08/28/2014 03:13 PM, Richard Biener wrote:
knowledge of scopes and such, only available in the FE. Is there a
generic way of determining if a DECL is in global scope?
Via DECL_CONTEXT and the global scope macro predicate. Eventually not enough
to detect class scope statics.
This patch fixes up varpool nodes after LIPO linking as we were doing
for cgraph node references. While, here I made some fixes to the
cgraph fixup as well (mark address taken as appropriate) and removed
old references. The latter exposed an issue with resolved cgraph nodes
getting eliminated when
On Thu, Aug 28, 2014 at 1:40 PM, Xinliang David Li davi...@google.com wrote:
Do you know why the previous check is not enough ?
cgraph_can_remove_if_no_direct_calls_and_refs_p (struct cgraph_node *node)
This will return true for the external node, but it also returns true
for the non-external
ok. The patch is fine.
On Thu, Aug 28, 2014 at 1:46 PM, Teresa Johnson tejohn...@google.com wrote:
On Thu, Aug 28, 2014 at 1:40 PM, Xinliang David Li davi...@google.com wrote:
Do you know why the previous check is not enough ?
cgraph_can_remove_if_no_direct_calls_and_refs_p (struct
On Aug 28, 2014, at 7:27 AM, Bernd Schmidt ber...@codesourcery.com wrote:
The next question would be what to do with gcc.c-torture/unsorted. As far as
I can tell, these are all just plain compile tests, except for dump-noaddr.c.
Ok to move all except for that test to c-torture/compile,
AArch64 maintainers, could you help to review following patches?
https://gcc.gnu.org/ml/gcc-patches/2014-08/msg01966.html
https://gcc.gnu.org/ml/gcc-patches/2014-08/msg02060.html
thanks
Guozhi Wei
On Wed, Aug 20, 2014 at 12:51 PM, Carrot Wei car...@google.com wrote:
Good suggestion. Add the
Hi!
The following patch silences two warnings in the mep-elf target,
fixing the config-list.mk build:
First one:
~~
g++ -c -DIN_GCC_FRONTEND -DIN_GCC_FRONTEND -g -O2 -DIN_GCC
-DCROSS_DIRECTORY_STRUCTURE -fno-exceptions -fno-rtti
-fasynchronous-unwind-tables -W -Wall -Wno-narrowing
On Thu, Aug 28, 2014 at 3:00 PM, Jan-Benedict Glaw jbg...@lug-owl.de wrote:
Hi!
The following patch silences two warnings in the mep-elf target,
fixing the config-list.mk build:
I thought -Werror was only on when the versions of GCC match.
Thanks,
Andrew
First one:
~~
g++ -c
This patch should fix it. Okay to apply?
Ok. Thanks!
2014-08-28 Jan-Benedict Glaw jbg...@lug-owl.de
* config/mep/mep-pragma.c (mep_pragma_coprocessor_subclass): Rework
to silence warning.
* config/mep/mep.c (VECTOR_TYPE_P): Remove duplicate definition.
On Tue, Aug 26, 2014 at 10:15 AM, David Malcolm dmalc...@redhat.com wrote:
On Mon, 2014-08-25 at 08:25 -0600, Jeff Law wrote:
On 08/19/14 15:35, David Malcolm wrote:
On Tue, 2014-08-19 at 13:57 -0700, Richard Henderson wrote:
On 08/06/2014 10:23 AM, David Malcolm wrote:
diff --git
Hi Cary,
Is the new patch ok for google-4_9?
Thanks,
Wei.
On Sun, Aug 24, 2014 at 8:53 PM, Wei Mi w...@google.com wrote:
To avoid the unused new discriminator value, I added a map
found_call_this_line to track whether a call is the first call in a
source line seen when assigning
On Thu, 2014-08-28 at 17:08 -0700, H.J. Lu wrote:
On Tue, Aug 26, 2014 at 10:15 AM, David Malcolm dmalc...@redhat.com wrote:
On Mon, 2014-08-25 at 08:25 -0600, Jeff Law wrote:
On 08/19/14 15:35, David Malcolm wrote:
On Tue, 2014-08-19 at 13:57 -0700, Richard Henderson wrote:
On
On 08/28/2014 05:47 PM, David Malcolm wrote:
- insn = as_a rtx_insn * (
-gen_extend_insn (op0, t, promoted_nominal_mode,
- data-passed_mode, unsignedp));
- emit_insn (insn);
+ rtx pat = gen_extend_insn (op0, t,
On Thu, 2014-08-28 15:47:07 -0700, Andrew Pinski pins...@gmail.com wrote:
On Thu, Aug 28, 2014 at 3:00 PM, Jan-Benedict Glaw jbg...@lug-owl.de wrote:
Hi!
The following patch silences two warnings in the mep-elf target,
fixing the config-list.mk build:
I thought -Werror was only on
On Thu, 2014-08-28 15:47:07 -0700, Andrew Pinski pins...@gmail.com wrote:
On Thu, Aug 28, 2014 at 3:00 PM, Jan-Benedict Glaw jbg...@lug-owl.de wrote:
The following patch silences two warnings in the mep-elf target,
fixing the config-list.mk build:
I thought -Werror was only on when the
The Go frontend had a bug comparing a struct or array value to an
interface value when the struct or array was not addressable. The code
that was supposed to force the struct/array into a temporary variable
did not fire, because the compiler erroneously tried to handle it as a
straight
Sorry for the context-less mail but I didn't find a proper
obvious gcc-patches-message to reply to. (Also, I can't log
into bugzilla because to enter a PR as there appears to have
been some SSL changes such that my old firefox and gcc.gnu.org
can no longer agree on a cipher or something.) But,
* doc/generic.texi: Fix typo.
---
gcc/ChangeLog|4
gcc/doc/generic.texi |2 +-
2 files changed, 5 insertions(+), 1 deletion(-)
diff --git a/gcc/ChangeLog b/gcc/ChangeLog
index ac5dc7c..01698e6 100644
--- a/gcc/ChangeLog
+++ b/gcc/ChangeLog
@@ -1,3 +1,7 @@
+2014-08-29
On Fri, Aug 29, 2014 at 02:55:36PM +0900, Honggyu Kim wrote:
--- a/gcc/doc/generic.texi
+++ b/gcc/doc/generic.texi
@@ -53,7 +53,7 @@ seems inelegant.
@node Deficiencies
@section Deficiencies
-There are many places in which this document is incomplet and incorrekt.
+There are many
86 matches
Mail list logo
