public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Martin v. Loewis" <martin@loewis.home.cs.tu-berlin.de>
To: zoluic@telostech.com
Cc: gcc-help@gcc.gnu.org
Subject: Re: String literals
Date: Wed, 05 Apr 2000 17:04:00 -0000	[thread overview]
Message-ID: <200004052356.BAA01094@loewis.home.cs.tu-berlin.de> (raw)
In-Reply-To: <38EB99A1.DA0D547E@telostech.com>

> I am having a problem running the enclosed test program. I expected
> program to pass the test points 1, 2 and 3 but instead it cored at
> point 2 (3). After looking into generated assembler code I noticed
> that string literals casted to array initializers (see pointers S2
> and s3) were put into read only segment. Is this correct (i.e. in
> compilance with ANSI C standard ) ?

Yes, this is indeed in compliance with the ISO C standard. gcc has an
option -fwritable-strings if you really need that function.

Regards,
Martin

      reply	other threads:[~2000-04-05 17:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-04-05 12:53 zeljko oluic
2000-04-05 17:04 ` Martin v. Loewis [this message]

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=200004052356.BAA01094@loewis.home.cs.tu-berlin.de \
    --to=martin@loewis.home.cs.tu-berlin.de \
    --cc=gcc-help@gcc.gnu.org \
    --cc=zoluic@telostech.com \
    /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).