public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "joseph at codesourcery dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/46261] avr-gcc: Segfaults when compiled with the -mint8 option
Date: Tue, 28 Jun 2011 19:06:00 -0000	[thread overview]
Message-ID: <bug-46261-4-gr6MkVTkXV@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-46261-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46261

--- Comment #19 from joseph at codesourcery dot com <joseph at codesourcery dot com> 2011-06-28 19:05:00 UTC ---
On Tue, 28 Jun 2011, gjl at gcc dot gnu.org wrote:

> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46261
> 
> --- Comment #18 from Georg-Johann Lay <gjl at gcc dot gnu.org> 2011-06-28 18:34:54 UTC ---
> (In reply to comment #17)
> > A) Include a new file, say avr/stdint.h, instead of newlib-stdint.h.
> > 
> > or
> > 
> > B) Include newlib-stdint.h prior to avr.h and override as needed.
> 
> or
> 
> C) Omit newlib-stdint.h altogether and to the defines in avr.h.
> 
> C) and A) are better than B)

Indeed, I simply made all bare-metal targets use newlib-stdint.h as a 
default, but since AVR has its own libc it seems more appropriate to put 
the defines in avr-stdint.h or avr.h and not use newlib-stdint.h.  (And 
the point of having separate headers such as newlib-stdint.h is that there 
may not otherwise be a header shared between all relevant targets.  If all 
AVR targets use avr-libc, putting the defines in avr.h makes sense, but if 
avr-rtems is using newlib like other RTEMS targets then you probably want 
a separate header only for AVR targets using avr-libc.)


  parent reply	other threads:[~2011-06-28 19:06 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-01 18:36 [Bug c/46261] New: " tnorth at fedoraproject dot org
2010-11-02 18:40 ` [Bug target/46261] " eric.weddington at atmel dot com
2010-11-02 18:45 ` tnorth at fedoraproject dot org
2011-01-25 17:02 ` k0l0b0k.void at gmail dot com
2011-05-01 13:32 ` bc-info at styx dot cabel.net
2011-05-01 17:28 ` tnorth at fedoraproject dot org
2011-05-01 17:28 ` tnorth at fedoraproject dot org
2011-05-01 17:31 ` tnorth at fedoraproject dot org
2011-06-26  9:58 ` gjl at gcc dot gnu.org
2011-06-26 19:42 ` gjl at gcc dot gnu.org
2011-06-27  5:43 ` eric.weddington at atmel dot com
2011-06-27  6:42 ` chertykov at gmail dot com
2011-06-27  8:02 ` j at uriah dot heep.sax.de
2011-06-27  8:31 ` gjl at gcc dot gnu.org
2011-06-27 21:49 ` eric.weddington at atmel dot com
2011-06-28  6:29 ` j at uriah dot heep.sax.de
2011-06-28  6:31 ` j at uriah dot heep.sax.de
2011-06-28 18:27 ` gjl at gcc dot gnu.org
2011-06-28 18:36 ` gjl at gcc dot gnu.org
2011-06-28 19:06 ` joseph at codesourcery dot com [this message]
2011-07-02 17:30 ` gjl at gcc dot gnu.org
2011-07-04 10:59 ` joseph at codesourcery dot com
2012-06-04  9:49 ` gjl at gcc dot gnu.org
2012-06-04  9:51 ` gjl at gcc dot gnu.org
2012-06-04  9:54 ` gjl at gcc dot gnu.org
2012-06-04  9:56 ` gjl at gcc dot gnu.org
2012-06-04 10:00 ` gjl at gcc dot gnu.org
2012-06-06 21:41 ` gjl at gcc dot gnu.org
2014-02-16 13:14 ` jackie.rosen at hushmail dot com

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-46261-4-gr6MkVTkXV@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).