public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
* Re: x86 assembler syntax
       [not found] <437286.10929.qm@web62003.mail.re1.yahoo.com>
@ 2010-08-17 15:58 ` Gerald Pfeifer
  0 siblings, 0 replies; 11+ messages in thread
From: Gerald Pfeifer @ 2010-08-17 15:58 UTC (permalink / raw)
  To: Rick Hodgin; +Cc: James Dennett, gcc

On Sun, 15 Aug 2010, Rick Hodgin wrote:
> For what it's worth. One of the pages I went to had the email address as 
> gcc@gnu.org, not even gcc@gcc.gnu.org. Somebody corrected me on that 
> already too. :-)

Both addresses -- gcc@gcc.gnu.org and gcc@gnu.org -- actually work,
interchangably.  I did change our web page to only use the former
on Sunday to simplify things, cf. the bottom of http://gcc.gnu.org/ .

Thanks for your feedback!

Gerald

^ permalink raw reply	[flat|nested] 11+ messages in thread

* Re: x86 assembler syntax
  2010-08-17 22:50           ` David Edelsohn
@ 2010-08-18  3:56             ` Basile Starynkevitch
  0 siblings, 0 replies; 11+ messages in thread
From: Basile Starynkevitch @ 2010-08-18  3:56 UTC (permalink / raw)
  To: David Edelsohn, gcc
  Cc: Ian Lance Taylor, James Dennett, Gerald Pfeifer, Rick C. Hodgin

On Tue, 2010-08-17 at 14:13 -0400, David Edelsohn wrote:
> On Mon, Aug 16, 2010 at 11:56 PM, Ian Lance Taylor <iant@google.com> wrote:
> > James Dennett <james.dennett@gmail.com> writes:
> >
> >> Apart from using the name gcc@gcc.gnu.org for the help list, and
> >> gcc-dev@gcc.gnu.org for developers (who should be able to find the
> >> right list)?
> >
> > I tend to agree that we should change the name of the gcc@gcc.gnu.org
> > mailing list.
> 
> Maybe instead of *changing* the name, we should *add*
> gcc-dev@gcc.gnu.org and re-purpose gcc@gcc.gnu.org.  


I would prefer having gcc-dev@gcc.gnu.org (which takes the role of
current gcc@gcc.gnu.org) and keeping the existing gcc-help@gcc.gnu.org

But if we re-purpose gcc@gcc.gnu.org we'll get there a lot of messages
asking for help. My feeling is that it is a much too used list to be
re-assigned.

Cheers.
-- 
Basile STARYNKEVITCH         http://starynkevitch.net/Basile/
email: basile<at>starynkevitch<dot>net mobile: +33 6 8501 2359
8, rue de la Faiencerie, 92340 Bourg La Reine, France
*** opinions {are only mine, sont seulement les miennes} ***

^ permalink raw reply	[flat|nested] 11+ messages in thread

* Re: x86 assembler syntax
  2010-08-17 11:06         ` Ian Lance Taylor
  2010-08-17 13:20           ` Richard Kenner
@ 2010-08-17 22:50           ` David Edelsohn
  2010-08-18  3:56             ` Basile Starynkevitch
  1 sibling, 1 reply; 11+ messages in thread
From: David Edelsohn @ 2010-08-17 22:50 UTC (permalink / raw)
  To: Ian Lance Taylor; +Cc: James Dennett, Gerald Pfeifer, Rick C. Hodgin, gcc

On Mon, Aug 16, 2010 at 11:56 PM, Ian Lance Taylor <iant@google.com> wrote:
> James Dennett <james.dennett@gmail.com> writes:
>
>> Apart from using the name gcc@gcc.gnu.org for the help list, and
>> gcc-dev@gcc.gnu.org for developers (who should be able to find the
>> right list)?
>
> I tend to agree that we should change the name of the gcc@gcc.gnu.org
> mailing list.

Maybe instead of *changing* the name, we should *add*
gcc-dev@gcc.gnu.org and re-purpose gcc@gcc.gnu.org.  Depending on how
we changed the existing mailinglist, it could create a lot of
unnecessary confusion or broken links (not that you suggested changing
the URL of the mailinglist archives).

- David

^ permalink raw reply	[flat|nested] 11+ messages in thread

* Re: x86 assembler syntax
  2010-08-17 11:06         ` Ian Lance Taylor
@ 2010-08-17 13:20           ` Richard Kenner
  2010-08-17 22:50           ` David Edelsohn
  1 sibling, 0 replies; 11+ messages in thread
From: Richard Kenner @ 2010-08-17 13:20 UTC (permalink / raw)
  To: iant; +Cc: foxmuldrster, gcc, gerald, james.dennett

> > Apart from using the name gcc@gcc.gnu.org for the help list, and
> > gcc-dev@gcc.gnu.org for developers (who should be able to find the
> > right list)?
> 
> I tend to agree that we should change the name of the gcc@gcc.gnu.org
> mailing list.

I don't think it'll help.  "gcc-dev: that's the list for people developing
software WITH gcc, right?"  ;-)

^ permalink raw reply	[flat|nested] 11+ messages in thread

* Re: x86 assembler syntax
  2010-08-16  8:56       ` James Dennett
@ 2010-08-17 11:06         ` Ian Lance Taylor
  2010-08-17 13:20           ` Richard Kenner
  2010-08-17 22:50           ` David Edelsohn
  0 siblings, 2 replies; 11+ messages in thread
From: Ian Lance Taylor @ 2010-08-17 11:06 UTC (permalink / raw)
  To: James Dennett; +Cc: Gerald Pfeifer, Rick C. Hodgin, gcc

James Dennett <james.dennett@gmail.com> writes:

> Apart from using the name gcc@gcc.gnu.org for the help list, and
> gcc-dev@gcc.gnu.org for developers (who should be able to find the
> right list)?

I tend to agree that we should change the name of the gcc@gcc.gnu.org
mailing list.

Ian

^ permalink raw reply	[flat|nested] 11+ messages in thread

* Re: x86 assembler syntax
  2010-08-16  5:46     ` Gerald Pfeifer
@ 2010-08-16  8:56       ` James Dennett
  2010-08-17 11:06         ` Ian Lance Taylor
  0 siblings, 1 reply; 11+ messages in thread
From: James Dennett @ 2010-08-16  8:56 UTC (permalink / raw)
  To: Gerald Pfeifer; +Cc: Rick C. Hodgin, gcc

On Sun, Aug 15, 2010 at 2:44 PM, Gerald Pfeifer <gerald@pfeifer.com> wrote:
> Hi Rick (and others),
>
> On Thu, 12 Aug 2010, Rick C. Hodgin wrote:
>>> This question would have been more appropriate on the gcc-help mailing
>>> list. -Ian Lance Taylor
>> My apologies to everyone.  I did not know such a list existed.
>
> all of our web pages have a footer which refers to gcc-help, but
> apparently this pointer is not working sufficiently well.
>
> This is _not_ to blame anyone, rather I'd like to see whether/how
> I can improve the situation.  Any suggestions?

Apart from using the name gcc@gcc.gnu.org for the help list, and
gcc-dev@gcc.gnu.org for developers (who should be able to find the
right list)?

Maybe it's too late for that, but it's unfortunate that the primary
mailing list name is taken for the implementors, not the users.

-- James

^ permalink raw reply	[flat|nested] 11+ messages in thread

* Re: x86 assembler syntax
  2010-08-13  4:16   ` Rick C. Hodgin
@ 2010-08-16  5:46     ` Gerald Pfeifer
  2010-08-16  8:56       ` James Dennett
  0 siblings, 1 reply; 11+ messages in thread
From: Gerald Pfeifer @ 2010-08-16  5:46 UTC (permalink / raw)
  To: Rick C. Hodgin; +Cc: gcc

Hi Rick (and others),

On Thu, 12 Aug 2010, Rick C. Hodgin wrote:
>> This question would have been more appropriate on the gcc-help mailing
>> list. -Ian Lance Taylor
> My apologies to everyone.  I did not know such a list existed.

all of our web pages have a footer which refers to gcc-help, but 
apparently this pointer is not working sufficiently well.

This is _not_ to blame anyone, rather I'd like to see whether/how
I can improve the situation.  Any suggestions?

Gerald

^ permalink raw reply	[flat|nested] 11+ messages in thread

* Re: x86 assembler syntax
  2010-08-13  4:10 ` Ian Lance Taylor
@ 2010-08-13  4:16   ` Rick C. Hodgin
  2010-08-16  5:46     ` Gerald Pfeifer
  0 siblings, 1 reply; 11+ messages in thread
From: Rick C. Hodgin @ 2010-08-13  4:16 UTC (permalink / raw)
  To: gcc

> "Rick C. Hodgin" <foxmuldrster@yahoo.com> writes:
> > Is there an Intel-syntax compatible option for GCC or G++?  And if not,
> > why not?  It's so much cleaner than AT&T's.
> -masm=intel
> This question would have been more appropriate on the gcc-help mailing
> list. -Ian Lance Taylor

My apologies to everyone.  I did not know such a list existed.

- Rick C. Hodgin


^ permalink raw reply	[flat|nested] 11+ messages in thread

* Re: x86 assembler syntax
  2010-08-09  6:42 Rick C. Hodgin
  2010-08-09  7:03 ` Tim Prince
@ 2010-08-13  4:10 ` Ian Lance Taylor
  2010-08-13  4:16   ` Rick C. Hodgin
  1 sibling, 1 reply; 11+ messages in thread
From: Ian Lance Taylor @ 2010-08-13  4:10 UTC (permalink / raw)
  To: Rick C. Hodgin; +Cc: gcc

"Rick C. Hodgin" <foxmuldrster@yahoo.com> writes:

> Is there an Intel-syntax compatible option for GCC or G++?  And if not,
> why not?  It's so much cleaner than AT&T's.

-masm=intel

This question would have been more appropriate on the gcc-help mailing
list.

Ian

^ permalink raw reply	[flat|nested] 11+ messages in thread

* Re: x86 assembler syntax
  2010-08-09  6:42 Rick C. Hodgin
@ 2010-08-09  7:03 ` Tim Prince
  2010-08-13  4:10 ` Ian Lance Taylor
  1 sibling, 0 replies; 11+ messages in thread
From: Tim Prince @ 2010-08-09  7:03 UTC (permalink / raw)
  To: gcc

On 8/8/2010 10:21 PM, Rick C. Hodgin wrote:
> All,
>
> Is there an Intel-syntax compatible option for GCC or G++?  And if not,
> why not?  It's so much cleaner than AT&T's.
>
> - Rick C. Hodgin
>
>
>    
I don't know how you get along without a search engine.  What about
http://tldp.org/HOWTO/Assembly-HOWTO/gas.html ?

-- 
Tim Prince

^ permalink raw reply	[flat|nested] 11+ messages in thread

* x86 assembler syntax
@ 2010-08-09  6:42 Rick C. Hodgin
  2010-08-09  7:03 ` Tim Prince
  2010-08-13  4:10 ` Ian Lance Taylor
  0 siblings, 2 replies; 11+ messages in thread
From: Rick C. Hodgin @ 2010-08-09  6:42 UTC (permalink / raw)
  To: gcc

All,

Is there an Intel-syntax compatible option for GCC or G++?  And if not,
why not?  It's so much cleaner than AT&T's.

- Rick C. Hodgin


^ permalink raw reply	[flat|nested] 11+ messages in thread

end of thread, other threads:[~2010-08-17 18:19 UTC | newest]

Thread overview: 11+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
     [not found] <437286.10929.qm@web62003.mail.re1.yahoo.com>
2010-08-17 15:58 ` x86 assembler syntax Gerald Pfeifer
2010-08-09  6:42 Rick C. Hodgin
2010-08-09  7:03 ` Tim Prince
2010-08-13  4:10 ` Ian Lance Taylor
2010-08-13  4:16   ` Rick C. Hodgin
2010-08-16  5:46     ` Gerald Pfeifer
2010-08-16  8:56       ` James Dennett
2010-08-17 11:06         ` Ian Lance Taylor
2010-08-17 13:20           ` Richard Kenner
2010-08-17 22:50           ` David Edelsohn
2010-08-18  3:56             ` Basile Starynkevitch

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).