On 16/04/15 06:12, Mikhail Maltsev wrote:
> So, I want to create a similar page in GCC's internal docs, but I don't
> know what should be included (i.e. did I miss something important, or
> did I include something obsolete), so I ask for some assistance.
The real challenge here is not generating t
Hi!
On Wed, 15 Apr 2015 10:31:59 +0200, Tom de Vries wrote:
> the link for 'ACM SIGPLAN Programming Languages Software Award' in the news
> list
> on gcc.gnu.org is http://www.sigplan.org/node/231, as discussed here (
> https://gcc.gnu.org/ml/gcc/2014-06/msg00136.html ).
>
> Following the lin
On 16/04/15 10:04, Andrew Haley wrote:
On 16/04/15 06:12, Mikhail Maltsev wrote:
So, I want to create a similar page in GCC's internal docs, but I don't
know what should be included (i.e. did I miss something important, or
did I include something obsolete), so I ask for some assistance.
The re
On Thu, Apr 16, 2015 at 08:12:17AM +0300, Mikhail Maltsev wrote:
> Hi, all!
>
> I think GCC documentation is missing a description of commonly used data
> structures and support functions. For example, "GCC internals" document
> contains information about, say, GIMPLE IR and functions for
> manipu
On 4/15/2015 10:38 PM, Alan Modra wrote:
> On Wed, Apr 15, 2015 at 04:10:33PM -0500, Joel Sherrill wrote:
>> Based on the grep, the .4byte directives are referencing a bogus symbol.
>>
>> Does this look like a GCC bug?
> Yes, unless you have some horrible asm there referencing the symbol.
>
Nope.
On 04/16/2015 02:22 PM, Manuel López-Ibáñez wrote:
> On 16/04/15 10:04, Andrew Haley wrote:
>> On 16/04/15 06:12, Mikhail Maltsev wrote:
>>> So, I want to create a similar page in GCC's internal docs, but I don't
>>> know what should be included (i.e. did I miss something important, or
>>> did I in
On 16 April 2015 at 17:15, Andrew Haley wrote:
> However, I am advising caution, particularly when documenting
> structures whose shape might soon change. And with respect to new
> contributions, it would be a shame if someone came along, did a great
> job of documenting the structures and interf
Joseph Myers writes ("Re: Selecting an architecture tuple for the Rumprun
toolchain"):
> If you would use a different glibc port, but providing access to
> Linux-specific interfaces, then the tuple would be
> ---gnu, much like *-*-kfreebsd-gnu describes a glibc
> port running on the FreeBSD ker
Snapshot gcc-4.8-20150416 is now available on
ftp://gcc.gnu.org/pub/gcc/snapshots/4.8-20150416/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 4.8 SVN branch
with the following options: svn://gcc.gnu.org/svn/gcc/branches
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hey,
We have changed our company name, hostnames and contact information.
Please remove the current BBLN mirror (mirror.bbln.org) and replace it
with our three new ones:
- ---
http://mirror0.babylon.network/gcc/
https://mirror0.babylon.network/g
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hey,
[[[ This is a confirmation of the request sent from n...@bbln.org ]]]
We have changed our company name, hostnames and contact information.
Please remove the current BBLN mirror (mirror.bbln.org) and replace it
with our three new ones:
- ---
11 matches
Mail list logo
