This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug fortran/31608] wrong types in character array/scalar binop
- From: "rguenther at suse dot de" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 25 Oct 2007 16:01:46 -0000
- Subject: [Bug fortran/31608] wrong types in character array/scalar binop
- References: <bug-31608-10053@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #43 from rguenther at suse dot de 2007-10-25 16:01 -------
Subject: Re: wrong types in character array/scalar binop
On Thu, 25 Oct 2007, Tobias dot Schlueter at physik dot uni-muenchen dot de
wrote:
>
>
> ------- Comment #42 from Tobias dot Schlueter at physik dot uni-muenchen dot de 2007-10-25 15:48 -------
> Subject: Re: wrong types in character array/scalar binop
>
> dave at hiauly1 dot hia dot nrc dot ca wrote:
> > ------- Comment #41 from dave at hiauly1 dot hia dot nrc dot ca 2007-10-25 15:41 -------
> > Subject: Re: wrong types in character array/scalar binop
> >
> >> While on x86_64-gnu-linux the dump has:
> >> int8 S.5;
> >> the variable on hppa-unknown-linux-gnu is:
> >> int4 S___5;
> >
> > I wonder why the variables names differ. I'm not aware of any
> > backend feature that controls this.
>
> Maybe (random shot in the dark) hp's assembler doesn't allow for dots in
> symbol names, and gcc, when generating the name for the symbol takes
> this into account even though this is on Linux?
gimplify.c:
tree
create_tmp_var_name (const char *prefix)
{
char *tmp_name;
if (prefix)
{
char *preftmp = ASTRDUP (prefix);
remove_suffix (preftmp, strlen (preftmp));
prefix = preftmp;
}
ASM_FORMAT_PRIVATE_NAME (tmp_name, prefix ? prefix : "T",
tmp_var_id_num++);
return get_identifier (tmp_name);
}
yes indeed.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31608