From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 29311 invoked by alias); 10 May 2008 01:09:11 -0000 Received: (qmail 29301 invoked by uid 22791); 10 May 2008 01:09:10 -0000 X-Spam-Check-By: sourceware.org Received: from fg-out-1718.google.com (HELO fg-out-1718.google.com) (72.14.220.155) by sourceware.org (qpsmtpd/0.31) with ESMTP; Sat, 10 May 2008 01:08:54 +0000 Received: by fg-out-1718.google.com with SMTP id e21so1003001fga.28 for ; Fri, 09 May 2008 18:08:50 -0700 (PDT) Received: by 10.86.84.5 with SMTP id h5mr9572522fgb.26.1210381730523; Fri, 09 May 2008 18:08:50 -0700 (PDT) Received: by 10.86.97.18 with HTTP; Fri, 9 May 2008 18:08:50 -0700 (PDT) Message-ID: <178adb870805091808p3be1ae42r63bce6fecc8d18ea@mail.gmail.com> Date: Sat, 10 May 2008 08:00:00 -0000 From: Omar To: "David Daney" Subject: Re: error: missing terminating " character while modifying md file Cc: gcc-help@gcc.gnu.org In-Reply-To: <4824E7D6.4050009@avtrex.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <178adb870805091651s16cb5417q98ed2a32c191eb10@mail.gmail.com> <4824E65D.8010802@avtrex.com> <4824E7D6.4050009@avtrex.com> Mailing-List: contact gcc-help-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-help-owner@gcc.gnu.org X-SW-Source: 2008-05/txt/msg00103.txt.bz2 On Fri, May 9, 2008 at 7:09 PM, David Daney 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