that - but if not, is this something we need to give a
bit more thought to?
(Please keep me cc'd, I'm not currently on this list)
Cheers,
Ron
On Mon, Aug 14, 2017 at 06:22:39PM +0100, Jonathan Wakely wrote:
> On 13 August 2017 at 19:20, Ron wrote:
> >
> > Hi,
> >
> > I'm looking for some clarification of how the __forced_unwind thread
> > cancellation exceptions intersect with noexcept
On Tue, Aug 15, 2017 at 01:31:10PM +0200, Richard Biener wrote:
> On Tue, Aug 15, 2017 at 1:28 PM, Jonathan Wakely
> wrote:
> > On 15 August 2017 at 11:24, Richard Biener
> > wrote:
> >> On Tue, Aug 15, 2017 at 6:44 AM, Ron wrote:
> >>> On Mon, Aug
On Tue, Aug 15, 2017 at 05:39:10PM +0100, Jonathan Wakely wrote:
> On 15 August 2017 at 16:21, Ron wrote:
> > On Tue, Aug 15, 2017 at 01:31:10PM +0200, Richard Biener wrote:
> >> On Tue, Aug 15, 2017 at 1:28 PM, Jonathan Wakely
> >> wrote:
> >> > On
On Tue, Aug 15, 2017 at 05:37:21PM +0100, Szabolcs Nagy wrote:
> On 15/08/17 16:47, Richard Biener wrote:
> > On Tue, Aug 15, 2017 at 5:21 PM, Ron wrote:
> >> Is changing the cancellation state really an expensive operation?
> >> Moreso than the checking which I assu
Hi,
I am teaching myself C by writing programs. I have some questions about
proper practices..
1) How do I know when to break my program into separate files. I am
currently working on a Star Trek program. It has 4 or 5 large
functions. They are all in one file. It's only about 900 lines rig
On Wed, Jan 11, 2006 at 12:03:42PM -0600, Perry Smith wrote:
> Is there a way to get some type of debugging output that tells me
> what line of C code produced what lines of asm code?
How about $TARGET-objdump --disassemble --source?
Ron
The GNU 4.1.2 C++ compiler is mangling typedef names to the point that they are
not retrievable from the DWARF data.
For example, the type BASE_UNION is defined as
typedef union
{
char ch;
int iVal;
long IVal;
} BASE_UNION;
The GNU 4.1.2 compiler generates the following DWARF data for
GNU
bug or just an unsupported feature?
Thanks.
--- On Fri, 1/22/10, Michael Eager wrote:
> From: Michael Eager
> Subject: Re: Mangled Typedef names in GNU 4.1.2 DWARF data?
> To: "Ron Louzon"
> Cc: gcc@gcc.gnu.org
> Date: Friday, January 22, 2010, 4:39 PM
> Ron Lou
of
code.
None of the powerpc-eabi code will depend on any
libraries or other external code, it will all be
completely self-contained.
Thanks!
Ron McCall
I guess I should have also mentioned that the
resultant program will be run under gdb, with a script
setting breakpoints, running, examining variables,
etc.
--- Paul Brook <[EMAIL PROTECTED]> wrote:
> > The call from Linux-land to eabi-land would not
> need
> > to pass arguments nor return anythi
You make a good point about the linker aspect but I was first most
concerned about the code generation differences, if any.
However, you are absolutely correct! A test is in order. I whipped up
a quick test program and was able to successfully compile, link and run
it, so it does indeed work!
a void *
pointer type). Is that not the case?
I am using gcc 4.0.3 and binutils 2.16.1 in case that
matters.
Just curious.
Ron McCall
On Wed, Sep 06, 2006 at 07:39:04PM -0400, Daniel Jacobowitz wrote:
> Yes, this is the convention we use.
>
> Void isn't a base type. The DWARF 3 standard way to represent this is
> DW_TAG_unspecified_type.
OK, thanks!
Ron
Available for download at:
http://people.redhat.com/lockhart/.GCC2007-Proceedings.pdf
-Ron
/**/
Ron Chen
Grid Engine Project:
http://gridengine.sunsource.net/
http://www.gridengine.info
15 matches
Mail list logo
