*
Call for Topics and Sponsors
Workshop on Open Source Development Tools 2015
Beijing, China
Sep. 12, 2015 (TBD)
HelloGCC Work Group (www.hellogcc.org)
*
On 06/25/2015 09:28 PM, Richard Sandiford wrote:
> Sorry in advance for inviting a bikeshed discussion, but while making
> the hashing changes that I just committed, I noticed that the C++ification
> has been done in a variety of different styles. I ended up having to follow
> the "do what the sur
On Thu, 2015-06-25 at 19:28 +0100, Richard Sandiford wrote:
> Sorry in advance for inviting a bikeshed discussion, but while making
> the hashing changes that I just committed, I noticed that the C++ification
> has been done in a variety of different styles. I ended up having to follow
> the "do w
On 06/25/2015 12:28 PM, Richard Sandiford wrote:
Sorry in advance for inviting a bikeshed discussion, but while making
the hashing changes that I just committed, I noticed that the C++ification
has been done in a variety of different styles. I ended up having to follow
the "do what the surroundi
On 25 June 2015 at 19:28, Richard Sandiford wrote:
> (2) Is there supposed to be a space before a template parameter list?
> I.e. is it:
>
>foo
>
> or:
>
>foo
>
> ? Both are widely used.
>
> The current coding conventions don't say explicitly, but all the
> exa
Sorry in advance for inviting a bikeshed discussion, but while making
the hashing changes that I just committed, I noticed that the C++ification
has been done in a variety of different styles. I ended up having to follow
the "do what the surrounding code does" principle that some code bases have,
On 25 June 2015 at 02:13, Mikhail Maltsev wrote:
> On 24.06.2015 13:41, Manuel López-Ibáñez wrote:
>> Is nobody seeing this? Is it a known problem with parallel make check?
>> If so, can we work-around it in compare_tests?
>>
>> Cheers,
>>
>> Manuel.
>>
> Actually I don't get such problem, but I r
On 06/09/2015 10:20 AM, Eric Botcazou wrote:
Because some folks don't want to audit their code to where to add byteswaps.
I am serious people have legacy big-endian code they want to run little
endian. There is a reason this is around in the first place. Developers are
lazy.
That's a little rou
On 06/09/2015 04:52 AM, Richard Biener wrote:
On Tue, Jun 9, 2015 at 12:39 PM, Eric Botcazou wrote:
What's the reason to not expose the byte swapping operations earlier, like
on GIMPLE? (or even on GENERIC?)
That would be too heavy, every load and store in GENERIC/GIMPLE would have an
associ
On 06/25/2015 06:28 AM, Richard Earnshaw wrote:
On 24/06/15 17:47, Jeff Law wrote:
On 06/24/2015 03:18 AM, Alan Modra wrote:
So in these examples we'd really like register moves to cost one
insn. Hmm, at least, moves from hard regs ought to cost something.
The more I think about it, the more
On 24/06/15 17:47, Jeff Law wrote:
> On 06/24/2015 03:18 AM, Alan Modra wrote:
>>
>> So in these examples we'd really like register moves to cost one
>> insn. Hmm, at least, moves from hard regs ought to cost something.
> The more I think about it, the more I think that's a reasonable step.
> Noth
11 matches
Mail list logo
