On Fri, Sep 04, 2015 at 06:04:15PM -0500, Segher Boessenkool wrote:
> On Fri, Sep 04, 2015 at 04:16:40PM -0400, Rich Felker wrote:
> > One thing I've noticed that's odd is that gcc -mfdpic -fPIC produces
> > different (less efficient) code from just gcc -mfdpic, which seems
> > wrong, but agrees wi
2015-09-05 1:50 GMT+03:00 Mike Stump :
>
> On Sep 4, 2015, at 2:45 PM, Ilya Verbin wrote:
>
>> 2015-09-04 22:27 GMT+03:00 Mike Stump :
>>> On Sep 4, 2015, at 4:10 AM, Hahnfeld, Jonas
>>> wrote:
>>> * intelmic-mkoffload.c (prepare_target_image): Fix if the temp path
>>> contains a '-‘
On Fri, Sep 04, 2015 at 04:16:40PM -0400, Rich Felker wrote:
> One thing I've noticed that's odd is that gcc -mfdpic -fPIC produces
> different (less efficient) code from just gcc -mfdpic, which seems
> wrong, but agrees with sh.c which has a number of checks for flag_pic
> not matched with a TARGE
This patch removes graphite-scop-detection.c:limit_scops function and fix
related issues arising because of that. The functionality limit_scop was added
as an intermediate step to discard the loops which graphite could not
handle. Removing limit_scop required handling of different cases of loops an
On Sep 4, 2015, at 2:45 PM, Ilya Verbin wrote:
> 2015-09-04 22:27 GMT+03:00 Mike Stump :
>> On Sep 4, 2015, at 4:10 AM, Hahnfeld, Jonas
>> wrote:
>> * intelmic-mkoffload.c (prepare_target_image): Fix if the temp path
>> contains a '-‘.
>>
>> So, out of curiosity, did you test all
> 2015-09-05 Janne Blomqvist
>
>PR fortran/53579
>* libgfortran.h (exit_error): New prototype.
>* runtime/error.c (exit_error): New function.
>(os_error): Call exit_error instead of exit.
>(runtime_error): Likewise.
>(runtime_error_at): Likewise.
>(internal_error): L
Hi,
the consesus in PR 53379 seems to be that a backtrace is desired in
case of error termination. The attached patch implements this.
Regtested on x86_64-pc-linux-gnu, Ok for trunk?
2015-09-05 Janne Blomqvist
PR fortran/53579
* libgfortran.h (exit_error): New prototype.
* runtim
2015-09-04 22:27 GMT+03:00 Mike Stump :
> On Sep 4, 2015, at 4:10 AM, Hahnfeld, Jonas
> wrote:
>* intelmic-mkoffload.c (prepare_target_image): Fix if the temp path
>contains a '-‘.
>
> So, out of curiosity, did you test all characters other than null? If -
> doesn’t work, there
On 09/04/2015 05:01 AM, Marek Polacek wrote:
While looking into something else I spotted this UB. I rewrote this
to use another UB, but I'd say left-shifting into the sign bit isn't
such an anathema as it was.
It's -Wshift-negative-value that warns on this. The reason why we haven't
seen the w
On 09/01/2015 07:08 AM, Ilya Enkovich wrote:
On 27 Aug 09:55, Richard Biener wrote:
I suggest you try modifying those parts first according to this
scheme that will most likely uncover issues we missed.
Thanks, Richard.
I tried to implement this scheme and apply it for MASK_LOAD and
MASK_STO
On 09/04/2015 09:27 AM, Jakub Jelinek wrote:
Hi!
This patch is a fix for gomp4.1 branch ICEs on
FAIL libgomp.c/for-5.c
FAIL libgomp.c++/for-13.C
that can be reproduced with intelmic emul offloading even on the trunk
with the attached testcase. The problem is that LTO streaming doesn't
really li
On 09/04/2015 08:29 AM, Marek Polacek wrote:
In this PR, we were crashing on an invalid asm. I think let's just reject
MODIFY_EXPRs as memory inputs - I'll wager those aren't meant to be supported
anyway.
Bootstrapped/regtested on x86_64-linux, ok for trunk?
2015-09-04 Marek Polacek
On 09/02/2015 11:26 PM, tbsaunde+...@tbsaunde.org wrote:
From: Trevor Saunders
gcc/ChangeLog:
2015-09-02 Trevor Saunders
* dse.c (store_info_t): Remove typedef.
(group_info_t): Likewise.
(const_group_info_t): Likewise.
(deferred_change_t): Likewise.
On 09/02/2015 11:26 PM, tbsaunde+...@tbsaunde.org wrote:
From: Trevor Saunders
gcc/ChangeLog:
2015-09-02 Trevor Saunders
* alias.c (alias_set_entry_d): Rename to alias_set_entry.
(alias_set_entry): Remove typedef.
(alias_set_subset_of): Adjust.
(alias_sets_c
On 09/02/2015 11:26 PM, tbsaunde+...@tbsaunde.org wrote:
From: Trevor Saunders
Hi,
Personally I think hiding that variables are pointers is confusing, and I
believe consensus is we should move away from this style. So this series
starts to do that.
patches individually bootstrapped + regtest
On 09/02/2015 05:02 PM, Georg-Johann Lay wrote:
Anatoliy Sokolov schrieb:
Hi.
The fixed_reg_set contain all fixed and global registers. This patch
change code "fixed_regs[r] || global_regs[r]" with "TEST_HARD_REG_BIT
(fixed_reg_set, r)".
Even though technically a no-op change
TEST_HARD_RE
On Thu, Sep 03, 2015 at 11:53:45AM -0400, Rich Felker wrote:
> On Thu, Sep 03, 2015 at 02:58:39PM +, Joseph Myers wrote:
> > On Wed, 2 Sep 2015, Rich Felker wrote:
> >
> > > So if __fpscr_values was the only reason for patch 1/3 in the FDPIC
> > > patchset, I think we can safely drop it. And p
On 09/03/2015 02:39 AM, Richard Sandiford wrote:
It sounds like Jeff has a much more radical rewrite in mind,
Certainly not anything on the immediate horizon. The amount of block
copying that'd be needed to isolate the jump threading path would be
significant.
I do wonder if we should be lo
The attached patch, committed as rev. 227502 after regtesting on
x86_64-apple-darwin15, removes an unused simplify function for MVBITS.
FX
z.diff
Description: Binary data
On Sep 4, 2015, at 4:10 AM, Hahnfeld, Jonas wrote:
* intelmic-mkoffload.c (prepare_target_image): Fix if the temp path
contains a '-‘.
So, out of curiosity, did you test all characters other than null? If -
doesn’t work, there is a good chance that no such test has been done, an
On Sep 4, 2015, at 8:02 AM, H.J. Lu wrote:
>> It's OK for me, but I can't approve it.
>
> I will check it in as an obvious fix.
Thanks, my 12/24 core box will appreciate it.
On September 4, 2015 5:27:27 PM GMT+02:00, Jakub Jelinek
wrote:
>Hi!
>
>This patch is a fix for gomp4.1 branch ICEs on
>FAIL libgomp.c/for-5.c
>FAIL libgomp.c++/for-13.C
>that can be reproduced with intelmic emul offloading even on the trunk
>with the attached testcase. The problem is that LTO s
On Fri, Sep 04, 2015 at 09:07:02PM +0300, Ilya Verbin wrote:
> It seems that there is a bug some here:
Thanks, will look at it on Monday.
> Here is the reproducer:
>
> #pragma omp declare target
> int a[1];
> #pragma omp end declare target
>
> void foo ()
> {
> #pragma omp target map(to: a[0:
Hi!
It seems that there is a bug some here:
On Wed, Jul 29, 2015 at 19:19:07 +0200, Jakub Jelinek wrote:
> @@ -12918,6 +12989,28 @@ lower_omp_target (gimple_stmt_iterator *
> var = var2;
> }
>
> + if (offloaded
> + && OMP_CLAUSE_MAP_KIND (c) == GOMP_MAP_FIRSTPRIVAT
All:
Thanks Jeff for the review comments.
The patch attached incorporate all the review comments given below.
Bootstrapped on i386 and Microblaze and the Deja GNU tests for Microblaze
results looks fine.
[Patch,tree-optimization]: Add new path Splitting pass on
tree ssa representation.
Added
Committed.
2015-09-02 10:51 GMT+03:00 Senthil Kumar Selvaraj
:
> Hi,
>
> This (rather trivial) patch fixes PR65210. The ICE happens because code
> wasn't handling io_low attribute where it is supposed to.
>
> If this is ok, could someone commit please? I don't have commit
> access.
>
> Reg
On 04/09/15 11:18 +0100, Jonathan Wakely wrote:
Tested powerpc64le-linux as normal, and again with #undef
_GTHREAD_USE_MUTEX_TIMEDLOCK to test the new code.
Argh, my testing with the 'undef didn't work because was
included after I had #undef'd it, so I wasn't testing the new code at
all, and i
Hi!
This patch is a fix for gomp4.1 branch ICEs on
FAIL libgomp.c/for-5.c
FAIL libgomp.c++/for-13.C
that can be reproduced with intelmic emul offloading even on the trunk
with the attached testcase. The problem is that LTO streaming doesn't
really like earlier unreferenced VAR_DECLs to be streame
Hi,
The attached test case that uses __builtin_unreachable in the default case
in a switch statement triggers a situation where a wrong instruction is placed
in the delay slot by the eager delay slot filler.
The issue should be reproducible with ToT compiler with -mips32r2 -G0
-mno-abicalls -O2.
I've been meaning to push this for a while. Primarily it removes two
set but never used private fields from the class and simplifies the
constructor in the obvious way. It also fixes a couple minor formatting
glitches, adds some missing comments, etc. It's ultimately related to
getting the
On Fri, Sep 4, 2015 at 7:59 AM, Christophe Lyon
wrote:
> On 4 September 2015 at 16:54, H.J. Lu wrote:
>> On Fri, Sep 4, 2015 at 7:52 AM, Christophe Lyon
>> wrote:
>>> On 4 September 2015 at 15:58, H.J. Lu wrote:
On Fri, Sep 4, 2015 at 6:15 AM, Christophe Lyon
wrote:
> On 4 Septem
On 4 September 2015 at 16:54, H.J. Lu wrote:
> On Fri, Sep 4, 2015 at 7:52 AM, Christophe Lyon
> wrote:
>> On 4 September 2015 at 15:58, H.J. Lu wrote:
>>> On Fri, Sep 4, 2015 at 6:15 AM, Christophe Lyon
>>> wrote:
On 4 September 2015 at 14:13, H.J. Lu wrote:
> On Fri, Sep 4, 2015 at
On Fri, Sep 4, 2015 at 7:52 AM, Christophe Lyon
wrote:
> On 4 September 2015 at 15:58, H.J. Lu wrote:
>> On Fri, Sep 4, 2015 at 6:15 AM, Christophe Lyon
>> wrote:
>>> On 4 September 2015 at 14:13, H.J. Lu wrote:
On Fri, Sep 4, 2015 at 4:47 AM, H.J. Lu wrote:
> On Fri, Sep 4, 2015 at 4
On 4 September 2015 at 15:58, H.J. Lu wrote:
> On Fri, Sep 4, 2015 at 6:15 AM, Christophe Lyon
> wrote:
>> On 4 September 2015 at 14:13, H.J. Lu wrote:
>>> On Fri, Sep 4, 2015 at 4:47 AM, H.J. Lu wrote:
On Fri, Sep 4, 2015 at 4:27 AM, H.J. Lu wrote:
> On Fri, Sep 4, 2015 at 4:18 AM, H
On Fri, Aug 28, 2015 at 8:50 AM, H.J. Lu wrote:
> Similar to as, ld, nm and objdump, gcc configure should check
> $READELF_FOR_TARGET for readelf.
>
> OK for trunk?
>
> H.J.
> ---
> PR bootstrap/67385
> * configure.ac (gcc_cv_readelf): Check $READELF_FOR_TARGET.
> * configu
In this PR, we were crashing on an invalid asm. I think let's just reject
MODIFY_EXPRs as memory inputs - I'll wager those aren't meant to be supported
anyway.
Bootstrapped/regtested on x86_64-linux, ok for trunk?
2015-09-04 Marek Polacek
PR inline-asm/67448
* gimplify.c (gim
Hi,
> Richard Sandiford writes:
> > Robert Suchanek writes:
> > > The patch below disables generation of the branch likely instructions for
> > > -
> Os
> > > but only for generic architecture. The branch likely may result in some
> > > code size reduction but the cost of running the code on R
On Fri, Sep 4, 2015 at 6:15 AM, Christophe Lyon
wrote:
> On 4 September 2015 at 14:13, H.J. Lu wrote:
>> On Fri, Sep 4, 2015 at 4:47 AM, H.J. Lu wrote:
>>> On Fri, Sep 4, 2015 at 4:27 AM, H.J. Lu wrote:
On Fri, Sep 4, 2015 at 4:18 AM, H.J. Lu wrote:
> On Thu, Sep 3, 2015 at 8:03 AM, C
OK.
Jason
On 4 September 2015 at 14:13, H.J. Lu wrote:
> On Fri, Sep 4, 2015 at 4:47 AM, H.J. Lu wrote:
>> On Fri, Sep 4, 2015 at 4:27 AM, H.J. Lu wrote:
>>> On Fri, Sep 4, 2015 at 4:18 AM, H.J. Lu wrote:
On Thu, Sep 3, 2015 at 8:03 AM, Christophe Lyon
wrote:
> On 3 September 2015 at 13:31
On Fri, Sep 04, 2015 at 01:31:09PM +0200, Jakub Jelinek wrote:
> On Fri, Sep 04, 2015 at 01:28:38PM +0200, Marek Polacek wrote:
> > I think it really doesn't make sense to instrument static initializers; we
> > wouldn't be able to error at run-time anyway. Besides, it causes a
> > compile-time
>
On Fri, Sep 4, 2015 at 4:47 AM, H.J. Lu wrote:
> On Fri, Sep 4, 2015 at 4:27 AM, H.J. Lu wrote:
>> On Fri, Sep 4, 2015 at 4:18 AM, H.J. Lu wrote:
>>> On Thu, Sep 3, 2015 at 8:03 AM, Christophe Lyon
>>> wrote:
On 3 September 2015 at 13:31, H.J. Lu wrote:
> On Wed, Sep 2, 2015 at 7:02 A
On Fri, Sep 4, 2015 at 4:27 AM, H.J. Lu wrote:
> On Fri, Sep 4, 2015 at 4:18 AM, H.J. Lu wrote:
>> On Thu, Sep 3, 2015 at 8:03 AM, Christophe Lyon
>> wrote:
>>> On 3 September 2015 at 13:31, H.J. Lu wrote:
On Wed, Sep 2, 2015 at 7:02 AM, Christophe Lyon
wrote:
> On 1 September 20
I think it really doesn't make sense to instrument static initializers; we
wouldn't be able to error at run-time anyway. Besides, it causes a compile-time
error. Generally, I think *compiling* with -fsanitize=undefined shouldn't add
any new compile-time errors. Yes, I know it does in some other
On Fri, Sep 04, 2015 at 01:28:38PM +0200, Marek Polacek wrote:
> I think it really doesn't make sense to instrument static initializers; we
> wouldn't be able to error at run-time anyway. Besides, it causes a
> compile-time
> error. Generally, I think *compiling* with -fsanitize=undefined should
> -Original Message-
> From: Ilya Verbin [mailto:iver...@gmail.com]
> Sent: Friday, September 04, 2015 1:23 PM
> To: Hahnfeld, Jonas; Jakub Jelinek
> Cc: gcc-patches@gcc.gnu.org; Kirill Yukhin
> Subject: Re: Fix intelmic-mkoffload.c if the temp path contains a '-'
>
> On Fri, Sep 04, 2015
On 04/09/15 11:18 +0100, Jonathan Wakely wrote:
This provides alternative implementations of std::timed_mutex and
std::recursive_timed_mutex for targets that don't support the
_POSIX_TIMEOUTS option (darwin and maybe HPUX).
Committed to trunk now.
On Fri, Sep 4, 2015 at 4:18 AM, H.J. Lu wrote:
> On Thu, Sep 3, 2015 at 8:03 AM, Christophe Lyon
> wrote:
>> On 3 September 2015 at 13:31, H.J. Lu wrote:
>>> On Wed, Sep 2, 2015 at 7:02 AM, Christophe Lyon
>>> wrote:
On 1 September 2015 at 16:04, Christophe Lyon
wrote:
> On 25 Au
On Fri, Sep 04, 2015 at 11:10:13 +, Hahnfeld, Jonas wrote:
> *ping*
> I don't have write access to the repository...
I've committed it to trunk:
https://gcc.gnu.org/viewcvs/gcc?view=revision&revision=227489
What about gcc-5-branch?
-- Ilya
On Thu, Sep 3, 2015 at 8:03 AM, Christophe Lyon
wrote:
> On 3 September 2015 at 13:31, H.J. Lu wrote:
>> On Wed, Sep 2, 2015 at 7:02 AM, Christophe Lyon
>> wrote:
>>> On 1 September 2015 at 16:04, Christophe Lyon
>>> wrote:
On 25 August 2015 at 17:31, Mike Stump wrote:
> On Aug 25, 20
On 14/08/15 12:01 -0400, Ed Smith-Rowland wrote:
OK.
This tested clean because it didn't install the headers.
So Jonathan. I am going to throw in the sponge on the configury.
Could you have a look and carry this over the finish line?
The main problem was in acinclude.m4:
+ GLIBCXX_CONDITI
> -Original Message-
> From: Hahnfeld, Jonas
> Sent: Tuesday, September 01, 2015 1:54 PM
> To: 'Jakub Jelinek'
> Cc: gcc-patches@gcc.gnu.org; Ilya Verbin; Kirill Yukhin
> Subject: RE: Fix intelmic-mkoffload.c if the temp path contains a '-'
>
> > -Original Message-
> > From: Jakub
I noticed that -Wshift-overflow isn't on by default even though now we're
defaulting to C++14. The reason is that at the time we set warn_shift_overflow
the cxx_dialect is still cxx_unset. So let's set the default C++ standard
earlier in that function, before be enable/disable the warnings.
(A t
This patch fixes a few -Wshift-negative-value warnings in the code. It
oughtn't to cause any functional changes. This will be needed for the
bootstrap to pass after I commit some other patch.
Bootstrapped/regtested on x86_64-linux, ok for trunk?
2015-09-03 Marek Polacek
* c-common.c
While looking into something else I spotted this UB. I rewrote this
to use another UB, but I'd say left-shifting into the sign bit isn't
such an anathema as it was.
It's -Wshift-negative-value that warns on this. The reason why we haven't
seen the warning before is due to a bug I'm fixing in the
Hello.
Following patch is a refactoring of ISA hierarchy related to
hsa_insn_basic class.
Thanks,
Martin
>From 9679925a23976db153b431d55f0f9cf7131f3886 Mon Sep 17 00:00:00 2001
From: mliska
Date: Thu, 3 Sep 2015 22:58:45 +0200
Subject: [PATCH 3/4] HSA: follow-up and refactoring of hsa_insn_basic
Hello.
Following patch adds a new IPA pass that creates clones intended to be
expanded to HSAIL. The pass is capable of LTO stuff.
Thanks,
Martin
>From 8cbddf693f93328f117dc48588deee924d2df6cd Mon Sep 17 00:00:00 2001
From: mliska
Date: Tue, 1 Sep 2015 14:10:24 +0200
Subject: [PATCH 1/4] HSA: cr
On Thu, Sep 03, 2015 at 04:16:50PM +0200, Jakub Jelinek wrote:
> On Wed, Sep 02, 2015 at 05:58:54PM +0200, Jakub Jelinek wrote:
> > Here is the start of the async offloading support I've talked about,
> > but nowait is not supported on the library side yet, only depend clause
> > (and for that I ha
This provides alternative implementations of std::timed_mutex and
std::recursive_timed_mutex for targets that don't support the
_POSIX_TIMEOUTS option (darwin and maybe HPUX).
The new versions need to use std::condition_variable, which depends on
std::mutex, so I have moved std::mutex, std::lock_
On Mon, Aug 24, 2015 at 10:17:19AM +0100, Alan Lawrence wrote:
> James Greenhalgh wrote:
> >
> > Did you check that these actually emit the expected instruction?
> >
> > Applying your patch set I see some fairly unpleasant code generation,
> > but I might have made an error, or perhaps you have a
On Tue, Aug 25, 2015 at 11:47:02AM +0100, Alan Lawrence wrote:
> James Greenhalgh wrote:
> >>
> >> - VAR1 (UNOP, vec_unpacks_hi_, 10, v4sf)
> >> + VAR2 (UNOP, vec_unpacks_hi_, 10, v4sf, v8hf)
> >
> > Should this not use the appropriate "BUILTIN_..." iterator?
>
> Indeed; BUILTIN_VQ_HSF it is.
>
Hi Christian,
Thanks again for working on this!
On 02/09/15 10:11, Christian Bruel wrote:
Hi,
This patch uses TARGET_OPTION_RESTORE and SAVE to switch the attribute
target dependent params between functions.
This is more efficient than arm_option_params_internal, and prepares the
ground for t
On 03/09/15 13:22 -0600, Martin Sebor wrote:
On 09/03/2015 04:58 AM, Jonathan Wakely wrote:
This change would allow including to be used to check for
__GLIBCXX__ and detect whether youre using libstdc++ or not. Howard
Hinnant recommends including that header for libc++ because it has no
other e
Steve Ellcey writes:
> Here is an update of my MIPS frame header optimization patch. This is
> actually only one part of the patch but I would like to get this approved
> and checked in before proceeding with the second half.
>
> The O32 ABI on MIPS requires that calling functions allocate spac
On 3 September 2015 at 20:28, Vladimir Makarov wrote:
> On 09/03/2015 11:00 AM, Vladimir Makarov wrote:
>>
>> On 09/02/2015 11:32 AM, Christophe Lyon wrote:
>>>
>>> Hi Vladimir,
>>>
>>>
>>>
>>> On 1 September 2015 at 21:39, Vladimir Makarov
>>> wrote:
The following patch is for
65 matches
Mail list logo
