Rietveld Code Review Tool
Help | Bug tracker | Discussion group | Source code | Sign in
(8726)

Issue 5229058: Rename some fields in struct language_function. (Closed)

Can't Edit
Can't Publish+Mail
Start Review
Created:
12 years, 6 months ago by Diego Novillo
Modified:
12 years, 6 months ago
Reviewers:
CC:
jason_redhat.com, gcc-patches_gcc.gnu.org
Visibility:
Public.

Patch Set 1 #

Unified diffs Side-by-side diffs Delta from patch set Stats (+10 lines, -10 lines) Patch
M gcc/cp/cp-tree.h View 2 chunks +10 lines, -10 lines 0 comments Download

Messages

Total messages: 2
Diego Novillo
This patch is needed in the pph branch because streamers need access to the fields ...
12 years, 6 months ago (2011-10-12 20:48:21 UTC) #1
jason_redhat.com
12 years, 6 months ago (2011-10-12 21:07:19 UTC) #2
On 10/12/2011 04:48 PM, Diego Novillo wrote:
> This patch is needed in the pph branch because streamers need access
> to the fields in struct language_function without going through
> cp_function_chain.
>
> Since these fields are named exactly like their #define counterparts,
> we cannot reference them without the pre-processor expanding the
> #defines, which causes build errors.
>
> -#define current_function_returns_value cp_function_chain->returns_value
> +#define current_function_returns_value cp_function_chain->x_returns_value
>
> -#define current_function_returns_null cp_function_chain->returns_null
> +#define current_function_returns_null cp_function_chain->x_returns_null
>
>   #define current_function_returns_abnormally \
> -  cp_function_chain->returns_abnormally
> +  cp_function_chain->x_returns_abnormally

Doesn't seem necessary for these three.  OK for in_*.

Jason

Sign in to reply to this message.

Powered by Google App Engine
RSS Feeds Recent Issues | This issue
This is Rietveld f62528b