public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "baker at usgs dot gov" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/28896] -fstack-limit-symbol and m68k and non 68020
Date: Tue, 18 Sep 2012 02:16:00 -0000	[thread overview]
Message-ID: <bug-28896-4-B2hE7wnx6t@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-28896-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #32 from Larry Baker <baker at usgs dot gov> 2012-09-18 02:16:32 UTC ---
Created attachment 28208
  --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=28208
Build patched GNU GCC 4.6.3 for ColdFire uClinux

Shell script to download, patch, and build GNU GCC 4.6.3 for ColdFire uClinux
target on Linux i386 host.


  parent reply	other threads:[~2012-09-18  2:16 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-28896-4@http.gcc.gnu.org/bugzilla/>
2012-07-03  7:29 ` schwab@linux-m68k.org
2012-07-03  9:46 ` schwab at gcc dot gnu.org
2012-07-03  9:47 ` schwab@linux-m68k.org
2012-07-03 23:44 ` baker at usgs dot gov
2012-07-04  1:40 ` baker at usgs dot gov
2012-08-09  2:06 ` baker at usgs dot gov
2012-08-09  2:16 ` baker at usgs dot gov
2012-08-12 21:24 ` baker at usgs dot gov
2012-08-12 21:28 ` baker at usgs dot gov
2012-08-12 21:30 ` baker at usgs dot gov
2012-08-15 21:38 ` baker at usgs dot gov
2012-08-15 21:43 ` steven at gcc dot gnu.org
2012-08-17 16:45 ` baker at usgs dot gov
2012-08-19  3:24 ` baker at usgs dot gov
2012-08-19 21:18 ` baker at usgs dot gov
2012-08-25  0:29 ` baker at usgs dot gov
2012-08-25  2:22 ` baker at usgs dot gov
2012-09-10 21:27 ` baker at usgs dot gov
2012-09-10 21:28 ` baker at usgs dot gov
2012-09-10 21:32 ` baker at usgs dot gov
2012-09-10 21:36 ` baker at usgs dot gov
2012-09-10 21:52 ` baker at usgs dot gov
2012-09-11 21:34 ` baker at usgs dot gov
2012-09-12 20:42 ` baker at usgs dot gov
2012-09-14 20:52 ` baker at usgs dot gov
2012-09-15  5:41 ` baker at usgs dot gov
2012-09-17 19:28 ` baker at usgs dot gov
2012-09-17 21:44 ` baker at usgs dot gov
2012-09-18  2:16 ` baker at usgs dot gov [this message]
2012-09-19  1:02 ` baker at usgs dot gov
2012-09-20  0:50 ` baker at usgs dot gov
2012-09-20  0:56 ` baker at usgs dot gov
2012-09-20 17:48 ` baker at usgs dot gov
2012-09-20 17:52 ` baker at usgs dot gov
2012-09-20 17:55 ` baker at usgs dot gov
2012-09-20 17:58 ` baker at usgs dot gov
2012-09-20 18:58 ` baker at usgs dot gov
2012-09-25 18:43 ` baker at usgs dot gov
2012-09-25 20:39 ` baker at usgs dot gov
2012-10-04 19:15 ` baker at usgs dot gov
2013-03-22 14:42 ` jakub at gcc dot gnu.org
2013-05-31 10:58 ` jakub at gcc dot gnu.org
2013-10-16  9:50 ` jakub at gcc dot gnu.org
2015-06-22 14:26 ` rguenth at gcc dot gnu.org
2006-08-30  6:14 [Bug target/28896] New: m68k port quietly accepts -fstack-limit-symbol on ColdFire kazu at gcc dot gnu dot org
2006-08-31  3:06 ` [Bug target/28896] -fstack-limit-symbol and m68k and non 68020 pinskia at gcc dot gnu dot org

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-28896-4-B2hE7wnx6t@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).