This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug target/36381] preprocessing, fortran: register include paths and framework


https://gcc.gnu.org/bugzilla/show_bug.cgi?id=36381

Eric Gallager <egallager at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |egallager at gcc dot gnu.org
           See Also|                            |https://gcc.gnu.org/bugzill
                   |                            |a/show_bug.cgi?id=36348

--- Comment #1 from Eric Gallager <egallager at gcc dot gnu.org> ---
(In reply to Daniel Franke from comment #0)
> Follow up to PR36348:
> 
> "[darwin-f.c] need[s] to implement darwin_register_frameworks, as well as
> the -iframework option implemented by handle_c_option in darwin-c.c. I
> suggest splitting that part of darwin-c.c into a new file darwin-cpp.c that
> is included in all three of c_target_objs, cxx_target_objs,
> fortran_target_objs.
>  
> Furthermore, given that the target hook TARGET_HANDLE_C_OPTION is
> implemented only by darwin-c.c, it makes sense to rename it to
> TARGET_HANDLE_CPP_OPTION and call it from the Fortran front-end too."
> 
> Reference: http://gcc.gnu.org/ml/fortran/2008-05/msg00348.html

Are you still working on this? If so, the status can be ASSIGNED, otherwise,
it'd make sense to remove yourself as the assignee.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]