Since there is already the __divtf3@GCC_3.0 compatibility alias in
libgcc we need to attach an explicit symbol version to the real __divtf3
in order to get it exported. This fixes the unversioned reference in
libgfortran.so, and fixes the failure of gfortran.dg/erf_3.F90. Tested
on ia64-suse-linu
On 11/21/2013 06:05 AM, Hans-Peter Nilsson wrote:
On Tue, 5 Nov 2013, Joseph S. Myers wrote:
Thanks for doing this! However, without examples I have trouble
reading out the bits I need as a target maintainer, and I can't
read out the answers from the patch, so pardon a few questions.
Support
On Thu, Nov 21, 2013 at 3:31 PM, Steven Bosscher wrote:
> On Thu, Nov 21, 2013 at 8:57 PM, Teresa Johnson wrote:
>> There are two problems I am fixing here (see
>> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59233 for full analysis).
>>
>> The first is the original ICE in crossjump optimization, w
On Thu, Nov 21, 2013 at 7:05 AM, Xinliang David Li wrote:
> Would it be sufficient to
>
> 1) get rid of the 'may_increase_size' parameter' in all the unroll
> interfaces (basically make it true for O2); and
> 2) set MAX_COMPLETELY_PEELED_INSNS parameter to be a smaller value for
> O2? -- this make
On 11/21/13 13:53, Cary Coutant wrote:
Let me rebase the
patch, kick off a bootstrap and regression tests, and I think I can be
ready to submit it if there are no objections.
Here's the rebased patch. I'm running the bootstrap and regression tests now.
The bootstrap passed with no new regress
On 11/21/2013 10:20 AM, Hans-Peter Nilsson wrote:
On Thu, 21 Nov 2013, Andrew MacLeod wrote:
Or is that part also required for
anything-other-than-ordinary-C-type alignment for the target;
say, natural 4-byte alignment of 4-byte-types for targets where
alignment is otherwise "packed"; where only
On Thu, Nov 21, 2013 at 2:12 PM, N.M. Maclaren wrote:
> On Nov 21 2013, Uros Bizjak wrote:
>>>
>>>
>>> Indeed, 387/SSE has flush-to-zero modes. But other APIs do not (glibc,
>>> SysV, AIX). I'm perfectly willing to add it, especially to 387/SSE, if given
>>> a bit of help (someone to write the ass
On Thu, 2013-11-21 at 12:22 +0100, Oleg Endo wrote:
> Sorry for the confusion. Initially I had it inserted right before
> machine dependent reorg, at which point I was getting nullptr from
> BLOCK_FOR_INSN all over the place. So not using it was the fix.
> However, only after I've noticed that SH
On Thu, Nov 21, 2013 at 12:19 AM, Zdenek Dvorak
wrote:
> Hi,
>
>> This patch works on the intrinsic calls handling issue in IVOPT mentioned
>> here:
>> http://gcc.gnu.org/ml/gcc-patches/2010-10/msg01295.html
>>
>> In find_interesting_uses_stmt, it changes
>>
>> arg = expr
>> __builtin_xxx (arg)
>
On 11/21/13 11:16, Andrew MacLeod wrote:
On 11/21/2013 01:15 PM, Andrew MacLeod wrote:
The second patch has the language front end changes. its only the
${language}-gimplify.c files which now actually require gimple.h
itself (yay). I also trimmed out the #includes which were introduced
but no
On Thu, 21 Nov 2013, Andrew MacLeod wrote:
> > I'm trying to avoid ABI breakage of course. I'd rather not have
> > to ask people not to use _Atomic with 4.9 for CRIS ports using
> > official releases or have ABI breakage with the next release.
> > Maybe there's one other port in the same situatio
On Thu, 2013-11-21 at 16:13 -0500, David Edelsohn wrote:
> On Thu, Nov 21, 2013 at 3:41 PM, Peter Bergner wrote:
> > * doc/extend.texi: Document htm builtins.
>
> LGTM.
Thanks, committed as revision 205233.
Peter
On Thu, Nov 21, 2013 at 4:39 PM, Marc Glisse wrote:
> On Thu, 21 Nov 2013, Cong Hou wrote:
>
>> While I added the new define_insn_and_split for vec_merge, a bug is
>> exposed: in config/i386/sse.md, [ define_expand "xop_vmfrcz2" ]
>> only takes one input, but the corresponding builtin functions ha
On Thu, Nov 21, 2013 at 5:09 PM, Martin Jambor wrote:
> Hi,
>
> the patch below enables IRA live-range splitting that later
> facilitates shrink-wrapping also work on ppc64. The difference is
> that while on x86_64 it was enough to look for single sets from a hard
> register to a pseudo in the fi
On 11/21/2013 11:32 AM, Joseph S. Myers wrote:
On Thu, 21 Nov 2013, Andrew MacLeod wrote:
I'm trying to avoid ABI breakage of course. I'd rather not have
to ask people not to use _Atomic with 4.9 for CRIS ports using
official releases or have ABI breakage with the next release.
Maybe there's o
On 11/21/2013 01:15 PM, Andrew MacLeod wrote:
The third patch has the config/* target changes, as well as a few
testcases. I did *not* trim out includes for the targets since I
got caught earlier with targets requiring some files on only some
configurations. I did go through an remove any
There are two problems I am fixing here (see
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59233 for full analysis).
The first is the original ICE in crossjump optimization, which was
exposed by enabling -freorder-blocks-and-partition which was
conservatively preventing some upstream block combining
>> Let me rebase the
>> patch, kick off a bootstrap and regression tests, and I think I can be
>> ready to submit it if there are no objections.
>
> Here's the rebased patch. I'm running the bootstrap and regression tests now.
The bootstrap passed with no new regressions. Do I need approval for
th
Richi,
Here is the patch. As you can see, i chose the unsigned option.
It was bootstrapped and tested on x86 with all languages including ada.
Ok to commit?
kenny
2013-11-21 zad...@naturalbridge.com
* store-layout.c
(place-field): Fix hwi test and accessor mismatch.
On 11/21/2013
Tobias,
> When I understand the patch correctly, the warning is shown in two cases:
> a) When the loop could be vectorized but the cost model prevented it
> b) When the loop couldn't be vectorized because of other reasons (e.g. not
> vectorizable because of conditional loop exits, incomplete vect
On 11/21/2013 01:15 PM, Andrew MacLeod wrote:
The second patch has the language front end changes. its only the
${language}-gimplify.c files which now actually require gimple.h
itself (yay). I also trimmed out the #includes which were introduced
but not required there as well.
* ada/gcc
Michael,
Thanks for working to improve this feature.
I think that testing on a few more targets would be advisable because
other targets may expose problems caused by the effects of
optimizations exposed by better "restrict" implementation.
Thanks, David
Thanks for the comments.
Regards,
Wei.
On Thu, Nov 21, 2013 at 12:48 AM, Bin.Cheng wrote:
> I don't know very much about the problem but willing to study since I
> am looking into IVO recently :)
>
>> --- tree-ssa-loop-ivopts.c (revision 204792)
>> +++ tree-ssa-loop-ivopts.c (working c
On Wed, Nov 20, 2013 at 7:54 PM, Jeff Law wrote:
> On 11/20/13 03:02, Richard Biener wrote:
>>
>>
>> Note that this, the intrusiveness of the feature and the questionable
>> gain makes me question whether GCC should have support for this
>> feature (and whether we really should rush this in this l
On Thu, Nov 21, 2013 at 7:27 PM, Bill Schmidt
wrote:
> Hi,
>
> This patch fixes two issues to allow correct compilation of
> gcc.dg/torture/vec-cvt-1.c in little endian mode. The first reverts a
> change in three patterns in vector.md. This is from an early patch that
> preceded the general fix
Hi,
This patch adds C implementation for intrinsics matching:
vmov[q]_n_f[32,64]
vmov[q]_n_[u,s,p][8,16]
vmov[q]_n_[u,s][32,64]
Regression tests for those intrinsics added.
Full regression test ran with no regressions. Tested with Big Endian.
Any objections?
Thanks,
Alex
2013-11-21 Alex Vel
Hi,
this is the required forward-propagation part for the type-demotion pass as
separate patch.
This patch is sharing some adjustments in testsuite due new optimization of
type-casts on shift-operations.
This patch tries to generate the "normal" form (TYPE) (X shift-op Y) out of the
"denormal"
On Thu, 21 Nov 2013, FX wrote:
> Indeed, 387/SSE has flush-to-zero modes. But other APIs do not (glibc,
> SysV, AIX).
Note that glibc libm functions may not work when called in a flush-to-zero
mode, only in modes that can be established by the functions.
If any argument to a function is subn
On Wed, Nov 20, 2013 at 5:33 PM, Ilya Enkovich wrote:
>>> CM_MEDIUM has unlimited data size.
>>>
>>> i386-opts.h: CM_MEDIUM,/* Assumes code fits in the low 31
>>> bits; data unlimited. */
>>>
>>> The x86_64_zext_immediate_operand allows _address_ to be loaded by
>>> movl. The @SIZE reloc
Hi,
Silvermont supports POPCNT. This patch enables POPCNT for Silvermont.
I also documented POPCNT for corei7, corei7-avx, core-avx-i, core-avx2 and
slm. Since POPCNT is enabled with -msse4.2, this patch doesn't change
code generation. It just makes it clear. OK to install?
Thanks.
H.J.
David,
Here comes the inevitable followup.. I broke backwards compatibility
when adding an extra field to ffi_cif. I'd like to import again from
upstream, where I've already fixed the problem.
https://sourceware.org/ml/libffi-discuss/2013/msg00220.html
Actually, it's not a straight import becau
On Thu, Nov 21, 2013 at 5:28 PM, Michael Meissner
wrote:
> With my changes for PR 59054, it broke several of the ISA 2.07 tests that I
> added due to DImode not being allowed in Altivec/VMX registers. This patch
> adjusts these tests to reflect the current code generation. In addition, it
> look
This all started with Stuart Hastings' original decloning patch way back
in 2002:
http://gcc.gnu.org/ml/gcc-patches/2002-08/msg00354.html
Bill Maddox tried to revive it in 2007:
http://gcc.gnu.org/ml/gcc-patches/2007-11/msg01147.html
I'm embarrassed that it has taken so long to get this in.
On Nov 21 2013, FX wrote:
That's a reasonable decision, but it is actually used at least ten
times as much as everything else put together, possibly a hundred times
as much.
I believe we are in pretty different parts of the community. Around me I
rarely see it used, while people check for n
On 2013/11/21 03:25 PM, Richard Henderson wrote:
> On 11/21/2013 02:41 PM, Chung-Lin Tang wrote:
>> I'm not saying we tolerate "wrong" RTL form, but rather that, it should
>> be an issue of the RTL passes, not the backend. The backend should just
>> be as much as possible, a "machine description".
Hi,
The attached patch reorganizes reduc_* operations in aarch64-simd.md and fixes
up lane accesses in arm_neon.h to conform to ABI changes.
Tested for aarch64-none-elf and aarch64_be-none-elf. OK for trunk?
Thanks,
Tejas Belagod
ARM.
2013-11-21 Tejas Belagod
gcc/
* config/aarch6
> I think most of these are because in the past (yes I have fixed that!!)
> all 'sizetype' constants were sign-extended (and the signedness,
> that is, TYPE_UNSIGNED (sizetype), was frontend dependend (ugh) and
> then later true, thus unsigned).
>
> So I think all _SIZE stuff should check fits_uhw
On Thu, Nov 21, 2013 at 3:41 PM, Peter Bergner wrote:
> The following patch documents the HTM built-in functions specific
> to POWER. I bootstrapped and reviewed the gcc.info file and
> everything looks good.
>
> Ok for mainline?
>
> Peter
>
>
> * doc/extend.texi: Document htm builtins.
On Thu, 21 Nov 2013, Andrew MacLeod wrote:
> If we add the hook for atomic_align_for_mode, and change the initalizers in
> tree.c, any target which doesnt need/use the hook should be unaffected. So
> everything remains as it is today.
>
> So Putting the hook in shouldn't be an issue. Then you can
On Thu, Nov 21, 2013 at 3:04 PM, Andrew MacLeod wrote:
> On 11/21/2013 02:26 PM, Jeff Law wrote:
>>
>> On 11/21/13 11:15, Andrew MacLeod wrote:
>>>
>>>
>>> Is there anything in particular one needs to do for plugins? I thought I
>>> saw a patch somewhere that changed something in the Makefile, but
On 11/21/2013 02:26 PM, Jeff Law wrote:
On 11/21/13 11:15, Andrew MacLeod wrote:
Is there anything in particular one needs to do for plugins? I thought I
saw a patch somewhere that changed something in the Makefile, but don't
know if that is actually required since I never did that for any of t
gcc/java
* class.c (maybe_layout_super_class): Update comment.
* decl.c (java_add_stmt): Remove use of input_filename macro.
* jcf-parse.c (set_source_filename): Remove use of
input_filename macro.
(parse_class_file): Remove use of input_line and input_filena
The following patch series eliminates the following macros that
implicitly use input_location:
input.h:
#define input_line LOCATION_LINE (input_location)
#define input_filename LOCATION_FILE (input_location)
#define in_system_header (in_system_header_at (input_location))
#define E
gcc/ada
* gcc-interface/utils2.c (build_call_raise): Remove use of
input_line macro.
(build_call_raise_range): Likewise.
(build_call_raise_column): Likewise.
---
gcc/ada/gcc-interface/utils2.c | 7 ---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git
gcc/c
* c-decl.c (define_label, shadow_tag_warned)
(check_bitfield_type_and_width, grokdeclarator, grokparms,
store_parm_decls_newstyle, store_parm_decls_oldstyle)
(declspecs_add_type): Remove use of in_system_header macro.
* c-parser.c (c_parser_unary_expre
gcc/c-family
* c-common.c (unsafe_conversion_p): Remove use of
EXPR_LOC_OR_HERE macro.
(conversion_warning): Likewise.
(warnings_for_convert_and_check): Likewise.
(warn_for_collisions_1): Likewise.
(shorten_compare): Likewise, and remove use of in_sy
gcc/
* config/bfin/bfin.c (output_file_start): Remove use of
input_filename macro.
---
gcc/config/bfin/bfin.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/gcc/config/bfin/bfin.c b/gcc/config/bfin/bfin.c
index d7af939..6fdf153 100644
--- a/gcc/config/bfin/bfin
gcc/
* builtins.c (c_strlen): Remove use of EXPR_LOC_OR_HERE macro.
* gimplify.c (internal_get_tmp_var): Likewise.
EXPR_LOC_OR_HERE macro.
(shortcut_cond_expr): Likewise.
* tree-diagnostic.c (diagnostic_report_current_function): Remove
use of input_fi
gcc/fortran
* trans.c (trans_runtime_error_vararg): Remove use of input_line
macro.
---
gcc/fortran/trans.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/gcc/fortran/trans.c b/gcc/fortran/trans.c
index 204cbff..7805b57 100644
--- a/gcc/fortran/trans.c
+++ b/gc
gcc/
* input.h (input_line): Remove.
(input_filename): Likewise.
(in_system_header): Likewise.
* tree.h (EXPR_LOC_OR_HERE): Remove.
---
gcc/input.h | 3 ---
gcc/tree.h | 2 --
2 files changed, 5 deletions(-)
diff --git a/gcc/input.h b/gcc/input.h
index 8fdc7b2..55
gcc/cp
* call.c (build_integral_nontype_arg_conv): Remove use of
EXPR_LOC_OR_HERE macro.
(convert_like_real): Likewise.
(convert_arg_to_ellipsis): Likewise.
(build_cxx_call): Likewise.
(perform_implicit_conversion_flags): Likewise.
(initialize
Hi,
This patch injects a condition into the instrumented code for edge
counter update. The counter value will not be updated after reaching
value 1.
The feature is under a new parameter --param=coverage-exec_once.
Default is disabled and setting to 1 to enable.
This extra check usually slows the
On 11/21/2013 01:24 PM, Joseph S. Myers wrote:
The new option should be able to use Var() in the .opt file rather than
having a variable defined explicitly or any explicit handling code in
c_common_handle_option, and shouldn't need to use UInteger (given the
option has no arguments).
Good point
Ping!
-Original Message-
From: Gopalasubramanian, Ganesh
Sent: Thursday, November 21, 2013 10:35 AM
To: 'H.J. Lu'
Cc: gcc-patches@gcc.gnu.org; Uros Bizjak (ubiz...@gmail.com); Richard Guenther
(richard.guent...@gmail.com);
borntrae...@de.ibm.com; Jakub Jelinek (ja...@redhat.com)
Subjec
On Tue, Nov 19, 2013 at 01:15:54PM +0100, Richard Biener wrote:
> On Mon, Nov 18, 2013 at 10:08 PM, Trevor Saunders
> wrote:
> > On Mon, Nov 18, 2013 at 10:03:53PM +0100, Marc Glisse wrote:
> >> On Mon, 18 Nov 2013, Trevor Saunders wrote:
> >>
> >> >This patch adds a class auto_vec which releases
On Fri, Nov 22, 2013 at 3:52 AM, H.J. Lu wrote:
> Silvermont supports POPCNT. This patch enables POPCNT for Silvermont.
> I also documented POPCNT for corei7, corei7-avx, core-avx-i, core-avx2 and
> slm. Since POPCNT is enabled with -msse4.2, this patch doesn't change
> code generation. It jus
PING.
Hi, there is a patch at
http://gcc.gnu.org/ml/gcc-patches/2013-09/msg01353.html which slipped away.
Thanks,
bin
Just something I noticed while looking at a problem tonight. We
threaded all the way back to the start of a jump threading path because
we didn't mark both blocks on the starting edge.
Bootstrapped and regression tested on x86_64-unknown-linux-gnu.
Installed on the trunk.
Jeff
* t
Right now jump threads from within a loop which cross the loop header,
then terminate within the loop are ignored as this may create
irreducible loops.
This patch gets the CFG/SSA updating code in good enough shape to handle
the case that the embedded guys care about. ie, the coremark FSA/F
101 - 159 of 159 matches
Mail list logo
