public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
* How to get info about `-ffixed-reg' by asm preprocessing?
@ 2005-01-15  1:56 Dmitry K.
  2005-03-23  4:41 ` list of known 2.95.2 bugs Marc E. Fiuczynski
  0 siblings, 1 reply; 4+ messages in thread
From: Dmitry K. @ 2005-01-15  1:56 UTC (permalink / raw)
  To: gcc-help

Hi.

How to obtain info about `-ffixed-reg' option by compiling
assembler-with-cpp program?

I have look `avr-cpp -dM -ffixed-r2 foo.S': no changes.

Thanks in advance.

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

* list of known 2.95.2 bugs
  2005-01-15  1:56 How to get info about `-ffixed-reg' by asm preprocessing? Dmitry K.
@ 2005-03-23  4:41 ` Marc E. Fiuczynski
  2005-03-23  5:02   ` Daniel Berlin
  0 siblings, 1 reply; 4+ messages in thread
From: Marc E. Fiuczynski @ 2005-03-23  4:41 UTC (permalink / raw)
  To: gcc-help

Could some kind soul point me at a web page that has a fairly complete list
of the known bugs in the 2.95.2 compiler?

Thanks,
Marc

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

* Re: list of known 2.95.2 bugs
  2005-03-23  4:41 ` list of known 2.95.2 bugs Marc E. Fiuczynski
@ 2005-03-23  5:02   ` Daniel Berlin
  2005-03-23  5:54     ` Marc E. Fiuczynski
  0 siblings, 1 reply; 4+ messages in thread
From: Daniel Berlin @ 2005-03-23  5:02 UTC (permalink / raw)
  To: Marc E. Fiuczynski; +Cc: gcc-help

On Tue, 2005-03-22 at 23:31 -0500, Marc E. Fiuczynski wrote:
> Could some kind soul point me at a web page that has a fairly complete list
> of the known bugs in the 2.95.2 compiler?
> 

Bug #1:  We don't have a list of bugs in the 2.95.2 compiler.


Seriously though, you should be able to get this kind of info from
bugzilla, querying for bugs reported against 2.95.

> Thanks,
> Marc
> 

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

* RE: list of known 2.95.2 bugs
  2005-03-23  5:02   ` Daniel Berlin
@ 2005-03-23  5:54     ` Marc E. Fiuczynski
  0 siblings, 0 replies; 4+ messages in thread
From: Marc E. Fiuczynski @ 2005-03-23  5:54 UTC (permalink / raw)
  To: Daniel Berlin; +Cc: gcc-help

Well, I am not sure what key words to use to zero in on the bug I am curious
about.

I have a switch statement that looks something like this:

	switch(protocol):
	case TCP:...break;
	case UDP:...break;
	case ICMP:
		if (!again){
			int a,b,c;
			...
			goto out;
		}

		out:
			...
		break;

	default:...break
	}

The break statement in the ICMP case seems to exist the scope of the switch
statement, but in a manner that it appears the stack pointer is hosed, as a
return from the function that contains this switch statement jumps to some
garbage value.

Given this, how would I best search gcc's bugzilla for this?  Simply
searching for "switch" or "break" requires a fairly long time (google
spoiled me) and I can't think of other keywords that might get me closer to
what I am looking for.

Marc


> -----Original Message-----
> From: Daniel Berlin [mailto:dberlin@dberlin.org]
> Sent: Tuesday, March 22, 2005 11:41 PM
> To: Marc E. Fiuczynski
> Cc: gcc-help@gcc.gnu.org
> Subject: Re: list of known 2.95.2 bugs
>
>
> On Tue, 2005-03-22 at 23:31 -0500, Marc E. Fiuczynski wrote:
> > Could some kind soul point me at a web page that has a fairly
> complete list
> > of the known bugs in the 2.95.2 compiler?
> >
>
> Bug #1:  We don't have a list of bugs in the 2.95.2 compiler.
>
>
> Seriously though, you should be able to get this kind of info from
> bugzilla, querying for bugs reported against 2.95.
>
> > Thanks,
> > Marc
> >

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

end of thread, other threads:[~2005-03-23  5:02 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2005-01-15  1:56 How to get info about `-ffixed-reg' by asm preprocessing? Dmitry K.
2005-03-23  4:41 ` list of known 2.95.2 bugs Marc E. Fiuczynski
2005-03-23  5:02   ` Daniel Berlin
2005-03-23  5:54     ` Marc E. Fiuczynski

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).