From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by sourceware.org (Postfix) with ESMTPS id 1C0823858D28 for ; Wed, 15 Feb 2023 17:08:01 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 1C0823858D28 Authentication-Results: sourceware.org; dmarc=pass (p=none dis=none) header.from=redhat.com Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=redhat.com DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1676480880; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=Un3jkSsmiOKBgakqTcYmGjJ37D9fu4cSuS4vzqPrndY=; b=YYBwMyLPBi/GpaPOOk7URIKl0F8M6VBklRZU6+YOCjsieiu79/S7lT5oSN12edmHkcoWZj g8XPeGn18zDkz3hyKQ+PyaaqPZ03lBgisY1Kkgp5D13Rmt2O+6iVFbd9Dq6QH1A2GQeLMd frJTf8QqhQUv8qDBKa7Z1me3FU08z4k= Received: from mail-qt1-f198.google.com (mail-qt1-f198.google.com [209.85.160.198]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_128_GCM_SHA256) id us-mta-68--sHq5SS6PN6RtQsjUwmFPA-1; Wed, 15 Feb 2023 12:07:59 -0500 X-MC-Unique: -sHq5SS6PN6RtQsjUwmFPA-1 Received: by mail-qt1-f198.google.com with SMTP id cd3-20020a05622a418300b003b9bd2a2284so11377561qtb.4 for ; Wed, 15 Feb 2023 09:07:55 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:in-reply-to:from:references:to :content-language:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=Un3jkSsmiOKBgakqTcYmGjJ37D9fu4cSuS4vzqPrndY=; b=v3Bb7CRyZ/OsRSpyj2uAG+dwGsEUQQMlIwDdJuIu3LV+UfZLxVXcbWOBdHeAGPU3tE AXP1thXiLsDLouGATVOslIGaYLf0nhWM0QqrTqdVKAh4HoKQqe+o0xVgFtRH9nwTRkRX OCQo3E/DI/Vnyaa7WhOnVtFlpLmNwSRZzt/VG5NkUlqlz+D4h4jmzg0tKSNXlso9xL27 /qM36N2At9jidZGQWgue6L/Fglz+AyzmdMlMZGw7RL+5uyDU3wt+wOnP7D6A5tvwMrfz ecRXk5MEpIZIzBz599qeD5CofsDPUvyCCcmrU3gYGk6CPRnnx2oGh70313rGuYHiY95J MpVg== X-Gm-Message-State: AO0yUKXKY9SDXde0zISa60x1Ic9i68nXk9nY3eFWTfuYfd2NXXc3RFAM BXTmQCAKlksFjRzpu0qcLjXoMYaRU6a1zgN6gYsuMJgRxi99gE63fuyIQ3ZfAtMJ1wZqH6Anm5B 42IfWqqN/JEQ3Aw7gl5XUwUo= X-Received: by 2002:ad4:5b8b:0:b0:56e:bc62:e151 with SMTP id 11-20020ad45b8b000000b0056ebc62e151mr5690463qvp.7.1676480875119; Wed, 15 Feb 2023 09:07:55 -0800 (PST) X-Google-Smtp-Source: AK7set/MSoqmZDfsZkvo71XHa1rqf3O1hmJAHZwavG4tNnInioNy4FWY2G4Ip/9OMqFn/jbnFTItQg== X-Received: by 2002:ad4:5b8b:0:b0:56e:bc62:e151 with SMTP id 11-20020ad45b8b000000b0056ebc62e151mr5690429qvp.7.1676480874867; Wed, 15 Feb 2023 09:07:54 -0800 (PST) Received: from [192.168.1.18] ([79.123.83.169]) by smtp.gmail.com with ESMTPSA id 79-20020a370852000000b007296805f607sm14115179qki.17.2023.02.15.09.07.53 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 15 Feb 2023 09:07:54 -0800 (PST) Message-ID: Date: Wed, 15 Feb 2023 17:07:53 +0000 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.7.1 Subject: Re: [RFC v0 0/6] ASCII Command for output section To: binutils@emagii.com, binutils@sourceware.org References: <20230215114052.28292-1-binutils@emagii.com> From: Nick Clifton In-Reply-To: <20230215114052.28292-1-binutils@emagii.com> X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Language: en-GB Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-3.2 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,NICE_REPLY_A,RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H2,SPF_HELO_NONE,SPF_NONE,TXREP autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: Hi Ulf, > I would like to support > > ASCII , > > when I try, and add > > ASCII 32 , "mystring" > > I get a "syntax error", and would like to understand why. Whilst I have not gone into this too deeply, I think that the short answer is "because that is the way that the linker's parser works". It expects numerical expressions, including constant integer values, to be enclosed in parentheses. > If I do: > ASCII () > I do not get a syntax error when I do > > ASCII (32) "mystring" Since this method works, I would suggest just sticking with it. Also, whilst using sprintf() to process escape sequences is a nice idea, it will not work. Escape sequences are a C language feature not a C library feature, so sprintf and its friends will not translate them for you. Cheers Nick