http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51883
Bug #: 51883
Summary: Build warning unknown conversion type in gimplify.c
Classification: Unclassified
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51883
--- Comment #2 from mdblack98 at yahoo dot com 2012-01-17 17:13:20 UTC ---
I should have realized that. Indeed those warning don't show up in later
stages.
Sorry for the noise.
-Original Message-
From: manu at gcc dot gnu.org [mailto:gcc
: unassigned at gcc dot gnu.org
Reporter: mdblack98 at yahoo dot com
Target Milestone: ---
subroutine foo(i,c)
use, intrinsic :: iso_c_binding, only: c_char
integer i
type, bind(C) :: params_block
character(kind=c_char,len=10) :: c
end type params_block
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84885
--- Comment #3 from mdblack98 at yahoo dot com ---
I'll correct my reply in that using len > 1 outside of an interoperability
block is OK.
So it is apparently now impossible to declare c_char len > 1 inside such a
block?
Mike
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84885
--- Comment #2 from mdblack98 at yahoo dot com ---
I got what's below from Steve Lionel of the FORTRAN working groupWith what
he said you flat should NOT be able to say anything other than LEN=1 for
c_char. Whether it's in a type block
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84885
--- Comment #5 from mdblack98 at yahoo dot com ---
I've been using Fortran since 1980 so caps is natural to me :-)
My concern is that if gfortran has supported the len>1 convention for many
years than perhaps it should continue support
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89373
mdblack98 at yahoo dot com changed:
What|Removed |Added
Status|RESOLVED|UNCONFIRMED
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: mdblack98 at yahoo dot com
Target Milestone: ---
Additional report from bug#89373
#include
// To see the bug
// gcc -DBUG -c x3.c
// Single item in braces is OK
// Multiple items in braces not OK
#ifdef BUG
#define
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89380
--- Comment #5 from mdblack98 at yahoo dot com ---
Why can't it be fixed by not counting commas between braces? That seems to be
the problem.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89373
--- Comment #4 from mdblack98 at yahoo dot com ---
FYI...the variadic macro __VA_ARGS__ did solve the braced items problem on
array initialization in nested macros. Just have to move the argument to the
end of the macro...
Thanks
Mike
: c
Assignee: unassigned at gcc dot gnu.org
Reporter: mdblack98 at yahoo dot com
Target Milestone: ---
include
#define MYMACRO1(m) MYLIST;
#define MYMACRO(r,m) \
MYMACRO##r(m)
#define MYLIST {1,2,3,4,5}
// too many args -- does not allow for braces such as used
11 matches
Mail list logo
