public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "gary at intrepid dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/20020] x86_64 - 128 bit structs not targeted to TImode
Date: Sun, 12 Aug 2012 22:44:00 -0000	[thread overview]
Message-ID: <bug-20020-4-gCuNCLUHgl@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-20020-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20020

--- Comment #28 from Gary Funck <gary at intrepid dot com> 2012-08-12 22:43:16 UTC ---
(In reply to comment #27)
> Please try this patch:
> 
> diff --git a/gcc/config/i386/i386.h b/gcc/config/i386/i386.h
> index c4d85b7..6c4c2ce 100644
> --- a/gcc/config/i386/i386.h
> +++ b/gcc/config/i386/i386.h
> @@ -1853,6 +1853,10 @@ do {                            \
> 
>  /* #define SLOW_UNALIGNED_ACCESS(MODE, ALIGN) 0 */
> 
> +/* An integer expression for the size in bits of the largest integer machine
> +   mode that should actually be used.  We allow pairs of registers.  */
> +#define MAX_FIXED_MODE_SIZE GET_MODE_BITSIZE (TARGET_64BIT ? TImode : DImode)
> +
>  /* Define this macro if it is as good or better to call a constant
>     function address than to call an address kept in a register.

That's the patch that I have been using and testing against (ref: comment #9).

I suggested this:
#define MAX_FIXED_MODE_SIZE targetm.scalar_mode_supported_p (TImode) ? TImode :
DImode
because it might allow x86 targets with SSE to also target TIMode for 128 bit
struct's (on the assumption that TImode will be more efficient).


  parent reply	other threads:[~2012-08-12 22:44 UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-20020-4@http.gcc.gnu.org/bugzilla/>
2011-07-08 16:22 ` gary at intrepid dot com
2011-07-08 17:00 ` gary at intrepid dot com
2011-07-08 17:21 ` gary at intrepid dot com
2011-07-09 10:28 ` ebotcazou at gcc dot gnu.org
2012-08-06 22:54 ` chip at pobox dot com
2012-08-11  3:23 ` gary at intrepid dot com
2012-08-11 14:38 ` hjl.tools at gmail dot com
2012-08-12 18:09 ` gary at intrepid dot com
2012-08-12 18:12 ` gary at intrepid dot com
2012-08-12 18:18 ` gary at intrepid dot com
2012-08-12 18:31 ` gary at intrepid dot com
2012-08-12 19:51 ` hjl.tools at gmail dot com
2012-08-12 21:25 ` gary at intrepid dot com
2012-08-12 21:46 ` gary at intrepid dot com
2012-08-12 21:48 ` gary at intrepid dot com
2012-08-12 21:51 ` gary at intrepid dot com
2012-08-12 22:09 ` gary at intrepid dot com
2012-08-12 22:15 ` gary at intrepid dot com
2012-08-12 22:31 ` hjl.tools at gmail dot com
2012-08-12 22:44 ` gary at intrepid dot com [this message]
2012-08-13  2:18 ` hjl.tools at gmail dot com
2012-08-14  4:26 ` gary at intrepid dot com
2012-08-14 22:47 ` chip at pobox dot com
2012-08-14 23:10 ` chip at pobox dot com
2012-08-14 23:44 ` hjl.tools at gmail dot com
2012-08-14 23:56 ` gary at intrepid dot com
2012-08-15  0:01 ` gary at intrepid dot com
2012-08-15  1:24 ` hjl.tools at gmail dot com
2012-08-15  3:35 ` gary at intrepid dot com
2012-08-15  8:58 ` rguenth at gcc dot gnu.org
2012-08-15  9:15 ` chip at pobox dot com
2012-08-15  9:30 ` rguenther at suse dot de
2012-08-15 13:48 ` gary at intrepid dot com
2012-08-15 13:59 ` hjl.tools at gmail dot com
2012-08-15 14:22 ` hjl.tools at gmail dot com
2012-08-15 14:46 ` gary at intrepid dot com
2012-08-15 14:56 ` jakub at gcc dot gnu.org
2012-08-15 16:02 ` hjl.tools at gmail dot com
2012-08-16  0:01 ` hjl.tools at gmail dot com
2012-08-17 20:01 ` hjl.tools at gmail dot com
2012-08-17 20:01 ` hjl at gcc dot gnu.org
2012-08-17 20:03 ` hjl at gcc dot gnu.org
     [not found] <bug-20020-9975@http.gcc.gnu.org/bugzilla/>
2008-08-03 17:45 ` ubizjak at gmail dot com
2005-02-17 13:46 [Bug target/20020] New: " gary at intrepid dot com
2005-02-17 14:04 ` [Bug target/20020] " pinskia at gcc dot gnu dot org
2005-02-17 16:44 ` matz at suse dot de
2005-02-17 23:25 ` gary at intrepid dot com
2005-02-17 23:51   ` Andrew Pinski
2005-02-17 23:52 ` pinskia at physics dot uc dot edu
2005-02-18  4:14 ` gary at intrepid dot com
2005-02-18  4:32 ` matz at suse dot de
2005-02-18  4:52 ` gary at intrepid dot com
2005-05-22 14:10 ` pinskia at gcc dot gnu dot org
2005-06-25 11:56 ` steven at gcc dot gnu dot org

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=bug-20020-4-gCuNCLUHgl@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /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).