public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Richard Biener <rguenth@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r12-6668] pack fields in cgraph_simd_clone_arg and struct function
Date: Tue, 18 Jan 2022 12:16:55 +0000 (GMT)	[thread overview]
Message-ID: <20220118121655.DB9963858020@sourceware.org> (raw)

https://gcc.gnu.org/g:d21db05b6f44f8cb6df8da5af276df0c4bb3a6c9

commit r12-6668-gd21db05b6f44f8cb6df8da5af276df0c4bb3a6c9
Author: Richard Biener <rguenther@suse.de>
Date:   Tue Jan 18 12:15:36 2022 +0100

    pack fields in cgraph_simd_clone_arg and struct function
    
    As pointed out by pahole.
    
    2022-01-18  Richard Biener  <rguenther@suse.de>
    
            * cgraph.h (struct cgraph_simd_clone_arg): Re-arrange fields to
            avoid padding.
            * function.h (struct function): Likewise.

Diff:
---
 gcc/cgraph.h   |  6 +++---
 gcc/function.h | 14 +++++++-------
 2 files changed, 10 insertions(+), 10 deletions(-)

diff --git a/gcc/cgraph.h b/gcc/cgraph.h
index a265107de58..43fc94e69ea 100644
--- a/gcc/cgraph.h
+++ b/gcc/cgraph.h
@@ -764,14 +764,14 @@ struct GTY(()) cgraph_simd_clone_arg {
      variable), uniform, or vector.  */
   enum cgraph_simd_clone_arg_type arg_type;
 
+  /* Variable alignment if available, otherwise 0.  */
+  unsigned int alignment;
+
   /* For arg_type SIMD_CLONE_ARG_TYPE_LINEAR_*CONSTANT_STEP this is
      the constant linear step, if arg_type is
      SIMD_CLONE_ARG_TYPE_LINEAR_*VARIABLE_STEP, this is index of
      the uniform argument holding the step, otherwise 0.  */
   HOST_WIDE_INT linear_step;
-
-  /* Variable alignment if available, otherwise 0.  */
-  unsigned int alignment;
 };
 
 /* Specific data for a SIMD function clone.  */
diff --git a/gcc/function.h b/gcc/function.h
index fb60979f9bd..098613766be 100644
--- a/gcc/function.h
+++ b/gcc/function.h
@@ -270,13 +270,6 @@ struct GTY(()) function {
   /* Value histograms attached to particular statements.  */
   htab_t GTY((skip)) value_histograms;
 
-  /* Different from normal TODO_flags which are handled right at the
-     beginning or the end of one pass execution, the pending_TODOs
-     are passed down in the pipeline until one of its consumers can
-     perform the requested action.  Consumers should then clear the
-     flags for the actions that they have taken.  */
-  unsigned int pending_TODOs;
-
   /* For function.cc.  */
 
   /* Points to the FUNCTION_DECL of this function.  */
@@ -338,6 +331,13 @@ struct GTY(()) function {
   unsigned int curr_properties;
   unsigned int last_verified;
 
+  /* Different from normal TODO_flags which are handled right at the
+     beginning or the end of one pass execution, the pending_TODOs
+     are passed down in the pipeline until one of its consumers can
+     perform the requested action.  Consumers should then clear the
+     flags for the actions that they have taken.  */
+  unsigned int pending_TODOs;
+
   /* Non-null if the function does something that would prevent it from
      being copied; this applies to both versioning and inlining.  Set to
      a string describing the reason for failure.  */


                 reply	other threads:[~2022-01-18 12:16 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20220118121655.DB9963858020@sourceware.org \
    --to=rguenth@gcc.gnu.org \
    --cc=gcc-cvs@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).