On Fri, Jul 04, 2014 at 09:57:11AM +0200, Tobias Grosser wrote:
> On 04/07/2014 04:16, Trevor Saunders wrote:
> >On Thu, Jul 03, 2014 at 07:52:59PM +0200, Tobias Grosser wrote:
> >>On 03/07/2014 19:23, Roman Gareev wrote:
> >>>Dear gcc contributors,
> >>>
> >>>could you please answer a few question
On 7/4/2014 12:08 AM, Hans-Peter Nilsson wrote:
Currently, c-cppbuiltin.c doesn't provide proper defines for this support.
> >We
> >currently define __GCC_HAVE_SYNC_COMPARE_AND_SWAP_4, etc, in
> >pa-linux.h.
I thought that was cheating! 1/2:)
> I'll experiment with defining ATOMIC_INT_LOCK_F
Hi all,
Consider code:
long int
foo (double a)
{
return __builtin_round (a);
}
Compiling for aarch64-none-elf (bare-metal aarch64 with newlib as
C-library) with -O2 gives the 003t.original dump:
;; Function foo (null)
;; enabled by -tree-original
{
return (long int) __builtin_round (a)
[ was: Re: combination of read/write and earlyclobber constraint modifier ]
On 02-07-14 17:52, Jeff Law wrote:
(by the way, in the same aarch64-simd.md file, I noticed some
define_expand with constraints, that looks strange)
It sometimes happens when a define_insn is converted into a define_exp
On 04/07/2014 04:16, Trevor Saunders wrote:
On Thu, Jul 03, 2014 at 07:52:59PM +0200, Tobias Grosser wrote:
On 03/07/2014 19:23, Roman Gareev wrote:
Dear gcc contributors,
could you please answer a few questions about std::map? Does gcc have
a policy that forbids using of map in the source cod
