public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: "Aaron J. Grier" <aaron@frye.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: libstdc++/5198: 3.0.3 linux x m68k build fail: invalid opcodes in c++locale.cc Date: Fri, 04 Jan 2002 14:36:00 -0000 [thread overview] Message-ID: <20020104223603.23856.qmail@sources.redhat.com> (raw) The following reply was made to PR libstdc++/5198; it has been noted by GNATS. From: "Aaron J. Grier" <aaron@frye.com> To: Don Lindsay <lindsayd@cisco.com> Cc: rodrigc@gcc.gnu.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, gcc-gnats@gcc.gnu.org Subject: Re: libstdc++/5198: 3.0.3 linux x m68k build fail: invalid opcodes in c++locale.cc Date: Fri, 4 Jan 2002 14:34:11 -0800 On Fri, Jan 04, 2002 at 01:53:00PM -0800, Don Lindsay wrote: > I see two questions: > - should the makefile be specifying -m68000? > (I'm out of practice on multilib rules, but I think the > MULTILIB_* stuff is asking for just that, and means to.) as far as I understand it, yes, since we're multilibbing here. > - given that -m68000 was on the command line, how come the assembler > output contains "casl" opcodes, which "as" tells us are only > present on the 68020 and up? > > I'm guessing that cc1 has to be fixed to not emit "casl" when invoked with > -m68000. the fault is with libstdc++-v3, specifically libstdc++-v3/config/cpu/m68k/bits/atomicity.h which includes "cas" as an inlined assembly instruction in a supposedly generic m68k include file. I've been able to identify at least three cases that need to be covered in atomicity.h: 68020/30/40: use current "cas" mcpu32 and v4 coldfire: "tas" on a static local variable 68000/010, v2/3 coldfire: disable interrupts disabling interrupts is rather heavy-handed, but I can't think of any other options for members of the m68k family that don't have test-and-set instructions. we don't know a priori how many threads will be waiting, so we can't use peterson's counting solution. (someone correct me if I'm wrong...) I'm also no m68k guru, and am not sure how many members of the m68k family gcc differentiates between, so the above list of cases may not be complete. I'm preparing a quick-and-dirty patch for people to go over, but if someone beats me to it, more power to them. :) -- Aaron J. Grier | Frye Electronics, Tigard, OR | aaron@frye.com "In a few thousand years people will be scratching their heads wondering how on earth the first computer was invented and bootstrapped without a prior computer to do it with." -- Chris Malcolm, on comp.arch
next reply other threads:[~2002-01-04 22:36 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-01-04 14:36 Aaron J. Grier [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-02-05 5:26 Werner Tuchan 2002-02-04 14:36 Aaron J. Grier 2002-02-04 11:06 Werner Tuchan 2002-01-23 17:41 rth 2002-01-08 13:56 Aaron J. Grier 2002-01-04 15:36 Aaron J. Grier 2002-01-04 14:46 Craig Rodrigues 2002-01-04 14:26 Craig Rodrigues 2002-01-04 13:56 Don Lindsay 2002-01-04 12:56 Craig Rodrigues 2002-01-04 12:26 Don Lindsay 2002-01-03 20:46 Craig Rodrigues 2002-01-03 20:16 Don Lindsay 2002-01-03 16:12 rodrigc 2002-01-03 15:47 rodrigc 2001-12-26 16:56 Don Lindsay 2001-12-26 16:20 rodrigc 2001-12-26 14:36 lindsayd
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=20020104223603.23856.qmail@sources.redhat.com \ --to=aaron@frye.com \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@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: linkBe 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).