On 13/07/2013, at 10:34 AM, Mike Stump wrote:
> On Jun 20, 2013, at 4:30 AM, Alexander Ivchenko wrote:
>> for Android:
>
>> +2013-06-19 Alexander Ivchenko
>> +
>> + * g++.dg/tls/thread_local4.C: Disable test for Android.
>> + * g++.dg/tls/thread_local4g.C: Ditto.
>
>> is it ok fo
These are nios2 patches for the gcc testsuite. Some new testcases were
added since the last posting.
Chung-Lin
2013-07-14 Sandra Loosemore
Chung-Lin Tang
Based on patches from Altera Corporation
* gcc.dg/stack-usage-1.c (SIZE): Define case for __nios2__.
nios2 libgcc parts. Since the original post, the only main change has
been the fdpbit vs soft-fp issue raised by Joseph, which has been
resolved. Other parts are mostly the same.
Thanks,
Chung-Lin
2013-07-14 Sandra Loosemore
Chung-Lin Tang
Based on patches from Altera
Original patch posted as part of Nios II patches:
http://gcc.gnu.org/ml/gcc-patches/2013-04/msg01087.html
This patch is to allow hexadecimal numbers to be used in option
arguments, e.g. -falign-loops=0x10 can now be used as equivalent to
-falign-loops=16.
Joseph, the patch has been modified to us
Ping.
On 2013/6/20 03:01 PM, Chung-Lin Tang wrote:
> Ping again?
>
> On 13/6/11 5:20 PM, Bernhard Reutner-Fischer wrote:
>> ping, CCing middle-end maintainers for review.
>>
>> On 31 May 2013 10:13, Chung-Lin Tang wrote:
>>> On 13/5/15 8:12 PM, Richard Sandiford wrote:
Chung-Lin Tang write
Hi,
The NeXT Objective C runtime and its interfaces have been evolving - and, in
particular, interfaces deprecated at Darwin9 have now been removed from recent
Darwin/OSX implementations.
The following patch:
(a) exchanges the use of Object with NSObject where appropriate, for Darwin
platforms
On Sun, 14 Jul 2013, Chung-Lin Tang wrote:
> Original patch posted as part of Nios II patches:
> http://gcc.gnu.org/ml/gcc-patches/2013-04/msg01087.html
>
> This patch is to allow hexadecimal numbers to be used in option
> arguments, e.g. -falign-loops=0x10 can now be used as equivalent to
> -fal
On Sun, Jul 14, 2013 at 07:39:38AM +0200, Marek Polacek wrote:
> This patch implements sanitizing of the __builtin_unreachable call.
> A call to __builtin_unreachable only emits BARRIER, if we actually get to it,
> the behavior is undefined. So, we just replace the call with a call to
> the ubsan
OK.
Jason
Applied, thanks.
Jason
On Sat, 13 Jul 2013, Jakub Jelinek wrote:
> Here is a patch that implements that (of course on top of Marek's patch from
> June).
>
> 2013-07-13 Jakub Jelinek
>
> * gcc.c: Document %{%:function(args):X}.
> (SANITIZER_EARLY_SPEC, SANITIZER_SPEC): Use %:sanitize(address)
> ins
On Sun, Jul 14, 2013 at 2:08 AM, Chung-Lin Tang wrote:
> Ping.
Could you please repost the patch with its description? This thread
is sufficiently old and noisy that I'm not even sure what the patch
does nor why.
Thanks. Diego.
On Sun, Jul 14, 2013 at 03:44:40PM +0200, Jakub Jelinek wrote:
> On Sun, Jul 14, 2013 at 07:39:38AM +0200, Marek Polacek wrote:
> > This patch implements sanitizing of the __builtin_unreachable call.
> > A call to __builtin_unreachable only emits BARRIER, if we actually get to
> > it,
> > the beha
On Thu, Jul 11, 2013 at 01:32:58AM +0200, Jakub Jelinek wrote:
> With this make check RUNTESTFLAGS=dg.exp=raw-string* passes, but perhaps
> I'll need to play with gcov and add some new testcases, e.g. ones
> I have in mind are R"??(??)??"; which wouldn't work correctly if we didn't
> stop consuming
Hi Tobias,
I think you should also handle:
module m
private
integer :: k
end module m
and
module m2
integer :: ll
end module m2
when compiled with -fmodule-private.
Taken care of in the attached patch, the way you suggested works.
Committed as rev. 200950.
Tha
Sorry, I haven't found time for this until now.
On Sunday 14 of July 2013, Jason Merrill wrote:
> On 07/08/2013 10:32 AM, Jason Merrill wrote:
> > Was it a deliberate decision to put this in the c-common attributes
> > rather than the C++-specific ones? I'm not saying it's wrong, just
> > inter
2013/7/13 JonY <10wa...@gmail.com>:
> On 7/10/2013 20:43, JonY wrote:
>> Hi,
>>
>> Attached are some minor patches, comments?
>>
>
> Kai, ping?
Please sent each patch as separate mail, and please add ChangeLogs for
them too. Additionally it would be fine to read some lines about
cause for those
On 07/14/2013 01:53 PM, Lubos Lunak wrote:
As for the copyright assignment, AFAIK there is a generic SUSE one that
should cover this as well.
Ah, yes.
Jason
On 7/15/2013 06:02, Kai Tietz wrote:
> 2013/7/13 JonY <10wa...@gmail.com>:
>> On 7/10/2013 20:43, JonY wrote:
>>> Hi,
>>>
>>> Attached are some minor patches, comments?
>>>
>>
>> Kai, ping?
>
>
> Please sent each patch as separate mail, and please add ChangeLogs for
> them too. Additionally it w
On 7/15/2013 06:02, Kai Tietz wrote:
> 2013/7/13 JonY <10wa...@gmail.com>:
>> On 7/10/2013 20:43, JonY wrote:
>>> Hi,
>>>
>>> Attached are some minor patches, comments?
>>>
>>
>> Kai, ping?
>
>
> Please sent each patch as separate mail, and please add ChangeLogs for
> them too. Additionally it w
On 7/15/2013 06:02, Kai Tietz wrote:
> 2013/7/13 JonY <10wa...@gmail.com>:
>> On 7/10/2013 20:43, JonY wrote:
>>> Hi,
>>>
>>> Attached are some minor patches, comments?
>>>
>>
>> Kai, ping?
>
>
> Please sent each patch as separate mail, and please add ChangeLogs for
> them too. Additionally it w
On Mon, Jul 15, 2013 at 09:15:27AM +0800, JonY wrote:
> On 7/15/2013 06:02, Kai Tietz wrote:
> > 2013/7/13 JonY <10wa...@gmail.com>:
> >> On 7/10/2013 20:43, JonY wrote:
> >>> Hi,
> >>>
> >>> Attached are some minor patches, comments?
> >>>
> >>
> >> Kai, ping?
> >
> >
> > Please sent each patch
Hi Michael,
> -Original Message-
> From: Michael Eager [mailto:ea...@eagerm.com]
> Sent: Saturday, 13 July 2013 9:33 am
> To: David Holsgrove
> Cc: gcc-patches@gcc.gnu.org; Edgar Iglesias; John Williams; Vinod Kathail;
> Vidhumouli Hunsigida; Nagaraju Mekala; Tom Shui
> Subject: Re: [Patch
Hi Michael,
On 18 March 2013 22:50, David Holsgrove wrote:
> Changelog
>
> 2013-03-18 David Holsgrove
>
> * gcc/config/microblaze/microblaze.h: Define SIZE_TYPE
>and PTRDIFF_TYPE.
>
> Signed-off-by: David Holsgrove
>
This patch remains the same, please review when ready.
thanks,
David
Hi Michael,
On 21 March 2013 03:00, Richard Henderson wrote:
> On 03/18/2013 05:48 AM, David Holsgrove wrote:
>> * gcc/config/microblaze/sync.md: New file.
>> * gcc/config/microblaze/microblaze.md: Add UNSPEC_SYNC_CAS,
>>UNSPEC_SYNC_XCHG and include sync.md.
>> * gcc/config/microblaze/micr
Hi Michael,
On 18 March 2013 22:49, David Holsgrove wrote:
> MicroBlaze doesn't have restrictions that would force us to
> reload regs via memory. Don't define SECONDARY_MEMORY_NEEDED.
> Fixes an ICE when compiling OpenSSL for linux.
>
> Changelog
>
> 2013-03-18 Edgar E. Iglesias
>
> * gcc/con
Hi Michael,
On 18 March 2013 22:52, David Holsgrove wrote:
> Changelog
>
> 2013-03-18 David Holsgrove
>
> * gcc/config/microblaze/microblaze.md (jump):
>Account for jumps to SYMBOL_REFs.
>
> Signed-off-by: David Holsgrove
>
Disregard - patch no longer desired.
thanks,
David
Hi Michael,
On 18 March 2013 22:48, David Holsgrove wrote:
> Changelog
>
> 2013-03-18 David Holsgrove
>
> * gcc/config/microblaze/microblaze.c (microblaze_expand_prologue):
>Add check for flag_stack_usage to handle -fstack-usage support
>
> Signed-off-by: David Holsgrove
>
Patch remains
MicroBlaze insn swaph swaps the contents of register rA as two
halfwords placing result in rD;
(rD)[0:15] <- (rA)[16:31]
(rD)[16:31] <- (rA)[0:15]
gcc bswaphi2 is intended to reverse the order of the bytes in the
half integer in rA
(rD)[8:15] <- (rA)[0:7]
(rD)[7:0] <- (rA)[8:15]
(rD)[24:31]
Add SImode to cstoresf4's comparison operator, prevents ICE during combine
rtl pass with error message;
internal compiler error: in simplify_subreg, at simplify-rtx.c:5725
Use ordered_comparison_operator predicate to limit operators to
those fcmp can handle, and letting compiler reorder insns to
To facilitate optimization pass understanding of the conditional
branch for microblaze, remove the UNSPEC'd signed_compare /
unsigned_compare instructions, and replace with a complete
branch_compare which will output_asm_insn the correct cmp/cmpu
depending on comparison code and signed / unsigned.
Some libubsan functions aren't really noreturn, so don't mark them as
such. This prevents failures with -O1+, since we don't generate any
code after calling noreturn routines, thus segfault when we actually
get there.
Applying to ubsan branch.
2013-07-15 Marek Polacek
* builtin-attrs
32 matches
Mail list logo
