public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "gnu at the-meissners dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/4605] [alpha-osf]mips-tfile & spaced directory names
Date: Tue, 13 Jan 2009 23:14:00 -0000	[thread overview]
Message-ID: <20090113231354.20377.qmail@sourceware.org> (raw)
In-Reply-To: <bug-4605-4970@http.gcc.gnu.org/bugzilla/>



------- Comment #15 from gnu at the-meissners dot org  2009-01-13 23:13 -------
I suspect this needs to be solved in gcc.c with the specs handling, and you
probably need something to quote the white space in filename, so that it
doesn't break the file into separate arguments.  Only some alpha and mips port
use ASM_FINAL_SPEC which calls mips-tfile.

I must admit that when I wrote mips-tfile as a quick hack in 1990 to get around
the problem of having to use the MIPS assembler which provided no debug
inteferface until a MIPS port of GAS was done, that the hack would still be in
use 18 years later.


-- 


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


  parent reply	other threads:[~2009-01-13 23:14 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-4605-4970@http.gcc.gnu.org/bugzilla/>
2009-01-07 15:40 ` ubizjak at gmail dot com
2009-01-12  9:53 ` markus dot schoepflin at comsoft dot de
2009-01-12 11:36 ` markus dot schoepflin at comsoft dot de
2009-01-12 11:43 ` markus dot schoepflin at comsoft dot de
2009-01-12 13:27 ` ubizjak at gmail dot com
2009-01-12 13:57 ` ubizjak at gmail dot com
2009-01-12 14:17 ` markus dot schoepflin at comsoft dot de
2009-01-12 14:59 ` ubizjak at gmail dot com
2009-01-12 19:51 ` markus dot schoepflin at comsoft dot de
2009-01-12 20:02 ` markus dot schoepflin at comsoft dot de
2009-01-13 23:14 ` gnu at the-meissners dot org [this message]
2009-01-14  8:12 ` markus dot schoepflin at comsoft dot de
     [not found] <bug-4605-4@http.gcc.gnu.org/bugzilla/>
2012-03-13  6:53 ` pinskia at gcc dot gnu.org
     [not found] <20011018011602.4605.andrae.behrens@sms-demag.de>
2003-05-25  2:39 ` dhazeghi@yahoo.com
2003-05-25  2:55 ` pinskia@physics.uc.edu

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=20090113231354.20377.qmail@sourceware.org \
    --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).