public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Sandiford <rsandifo@redhat.com>
To: Richard Henderson <rth@redhat.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: Fix x86 segfault on thread-local asm operands
Date: Sat, 29 Nov 2003 21:53:00 -0000	[thread overview]
Message-ID: <87brqvype2.fsf@redhat.com> (raw)
In-Reply-To: <20031128223211.GD5843@redhat.com>

Richard Henderson <rth@redhat.com> writes:
> Or perhaps you could use dg-error and add -Werror to the options?

OK, here's what I committed (after checking that the test case still passes).

Richard


	* stmt.c (expand_asm_operands): Check whether force_const_mem
	succeeded.

testsuite/
	* gcc.dg/tls/asm-1.C: New test.

Index: stmt.c
===================================================================
RCS file: /cvs/gcc/gcc/gcc/stmt.c,v
retrieving revision 1.336
diff -c -d -p -F^\([(a-zA-Z0-9_]\|#define\) -r1.336 stmt.c
*** stmt.c	20 Nov 2003 00:28:39 -0000	1.336
--- stmt.c	29 Nov 2003 18:50:25 -0000
*************** expand_asm_operands (tree string, tree o
*** 1712,1724 ****
  
  	      if (CONSTANT_P (op))
  		{
! 		  op = force_const_mem (TYPE_MODE (type), op);
! 		  op = validize_mem (op);
  		}
! 	      else if (GET_CODE (op) == REG
! 		       || GET_CODE (op) == SUBREG
! 		       || GET_CODE (op) == ADDRESSOF
! 		       || GET_CODE (op) == CONCAT)
  		{
  		  tree qual_type = build_qualified_type (type,
  							 (TYPE_QUALS (type)
--- 1712,1727 ----
  
  	      if (CONSTANT_P (op))
  		{
! 		  rtx mem = force_const_mem (TYPE_MODE (type), op);
! 		  if (mem)
! 		    op = validize_mem (mem);
! 		  else
! 		    op = force_reg (TYPE_MODE (type), op);
  		}
! 	      if (GET_CODE (op) == REG
! 		  || GET_CODE (op) == SUBREG
! 		  || GET_CODE (op) == ADDRESSOF
! 		  || GET_CODE (op) == CONCAT)
  		{
  		  tree qual_type = build_qualified_type (type,
  							 (TYPE_QUALS (type)
*** /dev/null	Tue Mar 19 20:01:09 2002
--- testsuite/gcc.dg/tls/asm-1.c	Sat Nov 29 18:49:09 2003
***************
*** 0 ****
--- 1,7 ----
+ /* { dg-options "-Werror" } */
+ __thread int i;
+ 
+ int foo ()
+ {
+   asm volatile ("" :: "m" (&i));	/* { dg-error "lvalue" } */
+ }

      reply	other threads:[~2003-11-29 18:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-28 16:32 Richard Sandiford
2003-11-28 22:43 ` Richard Henderson
2003-11-29 21:53   ` Richard Sandiford [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=87brqvype2.fsf@redhat.com \
    --to=rsandifo@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=rth@redhat.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).