# Scipy is replacing Fortran with C

**URL:** <https://fortran-lang.discourse.group/t/scipy-is-replacing-fortran-with-c/9059>\
**Category:** Uncategorized\
**Created:** [January 11, 2025, 11:57am UTC](https://fortran-lang.discourse.group/t/scipy-is-replacing-fortran-with-c/9059 "2025-01-11T11:57:11Z")\
**Posts on this page:** 1\
**Showing post:** 20

<div class="post-metadata">

**Author:** ![jwmwalrus](https://yyz2.discourse-cdn.com/free1/user_avatar/fortran-lang.discourse.group/jwmwalrus/32/4483_2.png) [@jwmwalrus](https://fortran-lang.discourse.group/u/jwmwalrus)\
**Post date:** [January 22, 2025, 12:30pm UTC](https://fortran-lang.discourse.group/t/scipy-is-replacing-fortran-with-c/9059/20 "2025-01-22T12:30:49Z")

</div>

> [@Marshdweller](#):
>
> Normally you use NVCC with another host compilers (gcc,g++, icc etc).

C compilers have this thing about providing their own `stddef.h` and then using whatever headers lie in the standard include paths (e.g., `/usr/include`).  
Fortran compilers on the other hand, went their separate ways some 40+ years ago and mixing stuff is now problematic —as @PierU mentioned, only the “Companion Processor” has that level of compatibility.

---

_[View the full topic](https://fortran-lang.discourse.group/t/scipy-is-replacing-fortran-with-c/9059)._