public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Omar <gcc.omar@gmail.com>
To: "David Daney" <ddaney@avtrex.com>
Cc: gcc-help@gcc.gnu.org
Subject: Re: error: missing terminating " character while modifying md file
Date: Sat, 10 May 2008 08:00:00 -0000	[thread overview]
Message-ID: <178adb870805091808p3be1ae42r63bce6fecc8d18ea@mail.gmail.com> (raw)
In-Reply-To: <4824E7D6.4050009@avtrex.com>

On Fri, May 9, 2008 at 7:09 PM, David Daney <ddaney@avtrex.com> wrote:
> David Daney wrote:
>>
>> Omar wrote:
>>>
>>>  Ok, so after weeks of reading and looking at multiple .md files, I
>>> felt ready to give it a try and decided to create some define_split's
>>> on my own.
>>>  I created a define_split RTL pattern which included this condition:
>>>  "reload_completed
>>>  && GET_CODE (operands[1]) == MEM
>>>  && GET_CODE (XEXP (operands[1], 0)) == PLUS"
>>>
>>> When I try to compile it I get:
>>> ../../gcc/config/c816/c816.md:36  error: missing terminating " character
>>> ../../gcc/config/c816/c816.md:37: error: stray '\' in program
>>> ...
>>>
>>> If instead, I place the condition all in a single line:
>>>  "reload_completed && GET_CODE (operands[1]) == MEM && GET_CODE (XEXP
>>> (operands[1], 0)) == PLUS"
>>> then gcc is happy.
>>>
>>> I have been searching the web for hours now, but I have not been able
>>> to find what is causing this.
>>> Does anyone have a suggestion on what might be causing this issue?
>>>
>>
>> It has to be a valid C string.  You get that error for the same reason
>> that you get it from this program:
>
> Well that must not be correct, please disregard it.  There are multi line
> conditions all over the place.
>
> Sorry for this mis-information.
>
> David Daney
>

Yes, I followed the convention used on other ports...
That's why I am puzzled with this. I do not think there is an issue
with specific piece of code, I am thinking
that it might be related with me using an outdated tool (gcc?) or
script interpreter (sh?). I might be completly out of touch
but that is my best guess at this moment.

 -Omar

  reply	other threads:[~2008-05-10  1:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-10  0:04 Omar
2008-05-10  0:10 ` David Daney
2008-05-10  1:09   ` David Daney
2008-05-10  8:00     ` Omar [this message]
2008-05-13  1:52       ` Omar Torres
2008-05-13  3:25         ` Tim Prince
2008-05-13  4:10           ` Omar Torres

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=178adb870805091808p3be1ae42r63bce6fecc8d18ea@mail.gmail.com \
    --to=gcc.omar@gmail.com \
    --cc=ddaney@avtrex.com \
    --cc=gcc-help@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).