This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [RFH] Uses of output.h in the front ends

From: Eric Botcazou <ebotcazou at adacore dot com>
To: David Edelsohn <dje dot gcc at gmail dot com>
Cc: Steven Bosscher <stevenb dot gcc at gmail dot com>, gcc at gcc dot gnu dot org, Jason Merrill <jason at redhat dot com>, Richard Guenther <richard dot guenther at gmail dot com>
Date: Wed, 6 Jun 2012 08:40:36 +0200
Subject: Re: [RFH] Uses of output.h in the front ends
References: <CABu31nPyeAW8_5o9+acP4A6_OCKhRJxY-_rLF6CQr5tjeVUcPg@mail.gmail.com> <201206051307.13140.ebotcazou@adacore.com> <CAGWvnymoZbnPe=Hz7ETPLjDWSy75SZqH0f2SV009hS_kq1+ZRg@mail.gmail.com>

> BSS was a later addition and there is no ".bss" pseudo-op directive,
> unlike the ".comm" directive. There only is the BSS storage class.

OK, thanks, this looks similar to the Tru64 situation.

-- 
Eric Botcazou

References:
- [RFH] Uses of output.h in the front ends
  - From: Steven Bosscher
- Re: [RFH] Uses of output.h in the front ends
  - From: Eric Botcazou
- Re: [RFH] Uses of output.h in the front ends
  - From: David Edelsohn

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]