public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Kaz Kojima <kkojima@rr.iij4u.or.jp>
To: gcc-patches@gcc.gnu.org
Cc: ro@CeBiTec.Uni-Bielefeld.DE, ubizjak@gmail.com
Subject: Re: [testsuite] Provide TLS access model testcases
Date: Sun, 29 May 2011 16:44:00 -0000	[thread overview]
Message-ID: <20110529.184205.389729669.kkojima@rr.iij4u.or.jp> (raw)
In-Reply-To: <yddhb8lwuih.fsf@manam.CeBiTec.Uni-Bielefeld.DE>

Hi,

Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE> wrote:
> 2010-12-30  Uros Bizjak <ubizjak@gmail.com>
> 	    Rainer Orth  <ro@CeBiTec.Uni-Bielefeld.DE>
> 
> 	* gcc.dg/torture/tls/run-gd.c: New test.
> 	* gcc.dg/torture/tls/run-ie.c: New test.
> 	* gcc.dg/torture/tls/run-ld.c: New test.
> 	* gcc.dg/torture/tls/run-le.c: New test.
> 	* lib/target-supports.exp (check_effective_target_tls_runtime):
> 	Build testcase with TLS options.

gcc.dg/torture/tls/run-gd.c fails on SH because SH assumes
-fpic for global and local dynamic tls models.  Although a line

/* { dg-options "-fpic" { target sh*-*-* } } */

added to run-gd.c and run-ld.c tests looks enough for SH,
I guess that target fpic instead of target sh*-*-* is more
reasonable because GD and LD tls models are usually for shared
objects.
I see similar failures on S390 testresults and it seems that
also S390 requires -fpic for GD and LD.
Give me your thoughts?

Regards,
	kaz

  reply	other threads:[~2011-05-29  9:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-23 13:53 Rainer Orth
2011-05-29 16:44 ` Kaz Kojima [this message]
2011-05-30 15:59   ` Rainer Orth
2011-05-31  7:53     ` Kaz Kojima
2011-06-07 11:54   ` Joseph S. Myers
2011-06-07 13:35     ` Kaz Kojima

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=20110529.184205.389729669.kkojima@rr.iij4u.or.jp \
    --to=kkojima@rr.iij4u.or.jp \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=ro@CeBiTec.Uni-Bielefeld.DE \
    --cc=ubizjak@gmail.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).