arm: Cannot handle identifiers with '$' character

[Debian Bug Importer]

Automatically imported from Debian bug report #327849 http://bugs.debian.org/327849

[Debian Bug Importer (debzilla)]

Automatically imported from Debian bug report #327849 http://bugs.debian.org/327849

[Matthias Klose (doko)]

arm is not an Ubuntu supported architecture

[Matthias Klose (doko-cs)]

> On arm only, gcc cannot handle C identifiers like:
>
> static void L1__GET_$ENVIRONMENT__defmacro()

please could you (or somebody having access to an arm machine) check,
if the problem exists in gcc-3.4 and/or gcc-snapshot as well?

if these fail as well, is it possible to build the package using
gcc-3.3 on arm?

[Phil Blundell (pb-reciva)]

On Mon, 2005-09-12 at 22:24 +0200, Matthias Klose wrote:
> > On arm only, gcc cannot handle C identifiers like:
> >
> > static void L1__GET_$ENVIRONMENT__defmacro()
>
> please could you (or somebody having access to an arm machine) check,
> if the problem exists in gcc-3.4 and/or gcc-snapshot as well?
>
> if these fail as well, is it possible to build the package using
> gcc-3.3 on arm?

>From what Camm told me before, it sounds like this problem only exists
in gcc-4.0.

I haven't investigated this issue at all, but at a first guess I would
say this is caused by the patches to support the new ARM EABI (in which
all identifiers containing $ are reserved). We should probably back out
that change in Debian, at least for the time being.

p.

[Camm Maguire (camm)]

Greetings! 3.4 too -- am backing off to 3.3 on arm now...
Take care,

Phil Blundell <email address hidden> writes:

> On Mon, 2005-09-12 at 22:24 +0200, Matthias Klose wrote:
> > > On arm only, gcc cannot handle C identifiers like:
> > >
> > > static void L1__GET_$ENVIRONMENT__defmacro()
> >
> > please could you (or somebody having access to an arm machine) check,
> > if the problem exists in gcc-3.4 and/or gcc-snapshot as well?
> >
> > if these fail as well, is it possible to build the package using
> > gcc-3.3 on arm?
>
> >From what Camm told me before, it sounds like this problem only exists
> in gcc-4.0.
>
> I haven't investigated this issue at all, but at a first guess I would
> say this is caused by the patches to support the new ARM EABI (in which
> all identifiers containing $ are reserved). We should probably back out
> that change in Debian, at least for the time being.
>
> p.
>
>
>
>

--
Camm Maguire <email address hidden>
==========================================================================
"The earth is but one country, and mankind its citizens." -- Baha'u'llah

[Debian Bug Importer (debzilla)]

Message-ID: <email address hidden>
Date: Mon, 12 Sep 2005 22:24:28 +0200
From: Matthias Klose <email address hidden>
To: <email address hidden>, Camm Maguire <email address hidden>
CC: <email address hidden>, <email address hidden>
Subject: Re: arm: Cannot handle identifiers with '$' character

> On arm only, gcc cannot handle C identifiers like:
>
> static void L1__GET_$ENVIRONMENT__defmacro()

please could you (or somebody having access to an arm machine) check,
if the problem exists in gcc-3.4 and/or gcc-snapshot as well?

if these fail as well, is it possible to build the package using
gcc-3.3 on arm?

[Debian Bug Importer (debzilla)]

Message-Id: <email address hidden>
Date: Mon, 12 Sep 2005 21:37:11 +0100
From: Phil Blundell <email address hidden>
To: Matthias Klose <email address hidden>
Cc: <email address hidden>, Camm Maguire <email address hidden>, <email address hidden>,
 <email address hidden>
Subject: Re: arm: Cannot handle identifiers with '$' character

On Mon, 2005-09-12 at 22:24 +0200, Matthias Klose wrote:
> > On arm only, gcc cannot handle C identifiers like:
> >
> > static void L1__GET_$ENVIRONMENT__defmacro()
>
> please could you (or somebody having access to an arm machine) check,
> if the problem exists in gcc-3.4 and/or gcc-snapshot as well?
>
> if these fail as well, is it possible to build the package using
> gcc-3.3 on arm?

>From what Camm told me before, it sounds like this problem only exists
in gcc-4.0.

I haven't investigated this issue at all, but at a first guess I would
say this is caused by the patches to support the new ARM EABI (in which
all identifiers containing $ are reserved). We should probably back out
that change in Debian, at least for the time being.

p.

[Debian Bug Importer (debzilla)]

Message-ID: <email address hidden>
Date: 15 Sep 2005 16:34:47 -0400
From: Camm Maguire <email address hidden>
To: Phil Blundell <email address hidden>
Cc: Matthias Klose <email address hidden>, <email address hidden>,
 <email address hidden>, <email address hidden>
Subject: Re: arm: Cannot handle identifiers with '$' character

Greetings! 3.4 too -- am backing off to 3.3 on arm now...
Take care,

Phil Blundell <email address hidden> writes:

> On Mon, 2005-09-12 at 22:24 +0200, Matthias Klose wrote:
> > > On arm only, gcc cannot handle C identifiers like:
> > >
> > > static void L1__GET_$ENVIRONMENT__defmacro()
> >
> > please could you (or somebody having access to an arm machine) check,
> > if the problem exists in gcc-3.4 and/or gcc-snapshot as well?
> >
> > if these fail as well, is it possible to build the package using
> > gcc-3.3 on arm?
>
> >From what Camm told me before, it sounds like this problem only exists
> in gcc-4.0.
>
> I haven't investigated this issue at all, but at a first guess I would
> say this is caused by the patches to support the new ARM EABI (in which
> all identifiers containing $ are reserved). We should probably back out
> that change in Debian, at least for the time being.
>
> p.
>
>
>
>

--
Camm Maguire <email address hidden>
==========================================================================
"The earth is but one country, and mankind its citizens." -- Baha'u'llah

[Matthias Klose (doko-mail)]

# submitted Debian report #327849 to gcc-gnats as PR 24111
# http://gcc.gnu.org/PR24111

forwarded 327849 http://gcc.gnu.org/PR24111
retitle 327849 [PR 24111] [3.4 4.0 4.1 regression] [arm] cannot handle identifiers with '$' character
tags 327849 + upstream
thanks

[Matthias Klose (doko-cs)]

severity 327849 important
thanks

-fdollars-in-identifiers work can be used as a workaround. see
http://gcc.gnu.org/PR24111 for the upstream report.

[Debian Bug Importer (debzilla)]

Message-Id: <email address hidden>
Date: Wed, 28 Sep 2005 22:43:00 +0200
From: Matthias Klose <email address hidden>
To: <email address hidden>
CC: <email address hidden>
Subject: gcc: submitted Debian report #327849 to gcc-gnats as PR 24111

# submitted Debian report #327849 to gcc-gnats as PR 24111
# http://gcc.gnu.org/PR24111

forwarded 327849 http://gcc.gnu.org/PR24111
retitle 327849 [PR 24111] [3.4 4.0 4.1 regression] [arm] cannot handle identifiers with '$' character
tags 327849 + upstream
thanks

[Debian Bug Importer (debzilla)]

Message-ID: <email address hidden>
Date: Wed, 28 Sep 2005 23:51:10 +0200
From: Matthias Klose <email address hidden>
To: <email address hidden>, Camm Maguire <email address hidden>
CC: <email address hidden>
Subject: cannot handle identifiers with '$' character

severity 327849 important
thanks

-fdollars-in-identifiers work can be used as a workaround. see
http://gcc.gnu.org/PR24111 for the upstream report.

[Falk Hueffner (falk)]

Hi,

As has been noted in http://gcc.gnu.org/PR24111, the default of not
allowing $ in identifiers is correct, so closing.

--
 Falk

[Debian Bug Importer (debzilla)]

Message-ID: <email address hidden>
Date: Sun, 02 Oct 2005 16:18:19 +0200
From: Falk Hueffner <email address hidden>
To: <email address hidden>
Subject: Bug#327849: [PR 24111] [3.4 4.0 4.1 regression] [arm] cannot handle
 identifiers with '$' character

Hi,

As has been noted in http://gcc.gnu.org/PR24111, the default of not
allowing $ in identifiers is correct, so closing.

--
 Falk

[Camm Maguire (camm)]

Greetings and thanks! I've put this in to gcl 2.6.7-10 -- we'll see
...

Take care,

Matthias Klose <email address hidden> writes:

> severity 327849 important
> thanks
>
> -fdollars-in-identifiers work can be used as a workaround. see
> http://gcc.gnu.org/PR24111 for the upstream report.
>
>
>

--
Camm Maguire <email address hidden>
==========================================================================
"The earth is but one country, and mankind its citizens." -- Baha'u'llah

[Debian Bug Importer (debzilla)]

Message-ID: <email address hidden>
Date: 13 Oct 2005 09:55:08 -0400
From: Camm Maguire <email address hidden>
To: Matthias Klose <email address hidden>
Cc: <email address hidden>, <email address hidden>
Subject: Re: cannot handle identifiers with '$' character

Greetings and thanks! I've put this in to gcl 2.6.7-10 -- we'll see
...

Take care,

Matthias Klose <email address hidden> writes:

> severity 327849 important
> thanks
>
> -fdollars-in-identifiers work can be used as a workaround. see
> http://gcc.gnu.org/PR24111 for the upstream report.
>
>
>

--
Camm Maguire <email address hidden>
==========================================================================
"The earth is but one country, and mankind its citizens." -- Baha'u'llah

[Bts-link-upstream (bts-link-upstream)]

# bts-link upstream status pull for source package gcc-4.0
# see http://lists.debian.org/debian-devel-announce/2006/05/msg00001.html
#
user <email address hidden>
usertags 33975 + status-NEW
usertags 55298 + status-NEW
usertags 75773 + status-NEW
usertags 86251 + status-NEW
tags 95318 + upstream
usertags 95318 + status-ASSIGNED
usertags 107123 + status-NEW
usertags 122103 + status-NEW
usertags 123468 + status-SUSPENDED
usertags 128950 + status-NEW
usertags 159838 + status-NEW
usertags 161432 + status-NEW
usertags 173513 + status-NEW
usertags 178561 + status-NEW
usertags 181096 + status-NEW
usertags 188943 + status-RESOLVED resolution-FIXED
usertags 195468 + status-NEW
usertags 201658 + status-NEW
usertags 204687 + status-ASSIGNED
usertags 211586 + status-NEW
usertags 212248 + status-ASSIGNED
usertags 215445 + status-NEW
usertags 221291 + status-NEW
usertags 227193 + status-RESOLVED resolution-FIXED
usertags 231748 + status-NEW
usertags 233673 + status-NEW
usertags 237207 + status-NEW
usertags 244894 + status-RESOLVED resolution-FIXED
usertags 247112 + status-RESOLVED resolution-FIXED
usertags 268115 + status-NEW
tags 270340 + fixed-upstream
usertags 270340 + status-RESOLVED resolution-FIXED
usertags 278310 + status-ASSIGNED
usertags 284777 + status-RESOLVED resolution-FIXED
usertags 301746 + status-NEW
usertags 317455 + status-RESOLVED resolution-FIXED
usertags 317563 + status-UNCONFIRMED
tags 318488 + fixed-upstream
usertags 318488 + status-RESOLVED resolution-FIXED
tags 318932 + fixed-upstream
usertags 318932 + status-RESOLVED resolution-FIXED
tags 319087 + fixed-upstream
usertags 319087 + status-RESOLVED resolution-FIXED
usertags 319309 + status-RESOLVED resolution-WONTFIX
tags 320947 + fixed-upstream
usertags 320947 + status-RESOLVED resolution-FIXED
usertags 321215 + status-REOPENED
tags 321785 + fixed-upstream
usertags 321785 + status-RESOLVED resolution-FIXED
usertags 323133 + status-RESOLVED resolution-FIXED
usertags 323686 + status-RESOLVED resolution-FIXED
usertags 323792 + status-UNCONFIRMED
usertags 324290 + status-NEW
usertags 324600 + status-NEW
tags 325050 + fixed-upstream
usertags 325050 + status-RESOLVED resolution-FIXED
tags 325131 + fixed-upstream
usertags 325131 + status-RESOLVED resolution-FIXED
usertags 325545 + status-RESOLVED resolution-FIXED
tags 326026 + fixed-upstream
usertags 326026 + status-RESOLVED resolution-FIXED
usertags 327346 + status-ASSIGNED
tags 327849 + fixed-upstream
usertags 327849 + status-RESOLVED resolution-INVALID
tags 328939 + fixed-upstream
usertags 328939 + status-RESOLVED resolution-FIXED
usertags 329694 + status-UNCONFIRMED
usertags 329840 + status-RESOLVED resolution-FIXED
tags 329845 + upstream
usertags 329845 + status-UNCONFIRMED
usertags 330279 + status-ASSIGNED
usertags 330564 + status-RESOLVED resolution-FIXED
tags 330857 + fixed-upstream
usertags 330857 + status-RESOLVED resolution-FIXED
tags 333100 + fixed-upstream
usertags 333100 + status-RESOLVED resolution-FIXED
usertags 333536 + status-NEW
usertags 335286 + status-RESOLVED resolution-FIXED
usertags 336915 + status-NEW
tags 340951 + upstream
usertags 340951 + status-REOPENED
usertags 344041 + status-ASSIGNED
tags ...