On Thu, Jun 25, 2015 at 7:03 PM, Jeff Law wrote:
> 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
> Well - they need a full audit anyway to slap those endian attributes on the
> appropriate structures. We are not, after all, introducing a -fbig-endian
> switch.
Sort of though, the Ada compiler has a pragma to tag all record types with an
SSO attribute (although I personally don't like it muc
Hello,
the libgomp has currently four config support directories: bsd, linux,
mingw32and posix. For RTEMS we use currently the POSIX config which has
however quite a huge run-time overhead. I would like to implement
something similar to the Linux futex based config. There are no unit
tests fo
As part of a project to clarify what behaviour of C implementations is
actually relied upon in modern practice, and what behaviour is
guaranteed by current mainstream implementations, we recently
distributed a survey of 15 questions about C, https://goo.gl/AZXH3S.
We were asking what C is in curre
On 25/06/15 17:27, Jeff Law wrote:
> 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 t
Hi,
On Thu, Jun 25, 2015 at 07:28:45PM +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 foll
On Thu, Jun 25, 2015 at 10:44 PM, Jeff Law wrote:
> 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
Hi,
On Thu, Jun 25, 2015 at 04:59:51PM -0400, David Malcolm wrote:
> 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 don
On 26 June 2015 at 10:40, Martin Jambor wrote:
>> (1) Should inline member functions be implemented inside the class or outside
>> the class? If inside, should they be formatted like this:
>
> https://gcc.gnu.org/codingconventions.html has a big section on C++
> (note that there is also a simi
On 06/26/2015 03:50 AM, Martin Jambor wrote:
Hi,
On Thu, Jun 25, 2015 at 04:59:51PM -0400, David Malcolm wrote:
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
On 06/26/2015 01:56 AM, Richard Biener wrote:
On Thu, Jun 25, 2015 at 7:03 PM, Jeff Law wrote:
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
endi
On Fri, 26 Jun 2015, Peter Sewell wrote:
> **If you calculate an offset between two separately allocated C memory
> objects (e.g. malloc'd regions or global or local variables) by
> pointer subtraction, can you make a usable pointer to the second by
> adding the offset to the address of the first?
On 26 June 2015 at 18:08, Joseph Myers wrote:
> On Fri, 26 Jun 2015, Peter Sewell wrote:
>
>> **If you calculate an offset between two separately allocated C memory
>> objects (e.g. malloc'd regions or global or local variables) by
>> pointer subtraction, can you make a usable pointer to the secon
On Fri, 26 Jun 2015, Peter Sewell wrote:
> > It's s simple matter of points-to analysis. &foo + anything may be
> > assumed (in practice) to point to something within foo (or just past the
> > end) and not to alias anything accessed through a pointer based on &bar.
> > If the compiler can see som
The GNU Compiler Collection version 4.9.3 has been released.
GCC 4.9.3 is a bug-fix release from the GCC 4.9 branch
containing important fixes for regressions and serious bugs in
GCC 4.9.2 with more than 110 bugs fixed since the previous release.
This release is available from the FTP servers list
Status
==
GCC 4.9.3 has been released, the branch is now open again
for regression and documentation fixes.
GCC 4.9.4 should be released some time after stage1 on the trunk
closes, in November or so.
Quality Data
Priority # Change from last report
---
On 26 June 2015 at 20:27, Joseph Myers wrote:
> On Fri, 26 Jun 2015, Peter Sewell wrote:
>
>> > It's s simple matter of points-to analysis. &foo + anything may be
>> > assumed (in practice) to point to something within foo (or just past the
>> > end) and not to alias anything accessed through a p
17 matches
Mail list logo
