https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63471
--- Comment #6 from dave.anglin at bell dot net --- On 10/8/2014 11:07 PM, jb at gcc dot gnu.org wrote: > That being said, googling this issue I stumbled upon > https://gcc.gnu.org/ml/gcc-patches/2011-03/msg00545.html where you fixed a > similar issue for hp-ux 10, seemingly by making the driver always set > _REENTRANT. Wouldn't a similar thing be the right thing to do for hp-ux 11 as > well? If there are no ill effects of always enabling _REENTRANT that would > help > other software than just libgfortran, as well as eliminating the risk that > unconditionally enabling _REENTRANT in libgfortran might break on some other > target? It's certainly easy to make the same change to hp-ux 11. I was clearly wrong about the guards being removed. I suspect HP introduced the _REENTRANT guard because they wanted to remove the _r routines: http://h21007.www2.hp.com/portal/download/files/unprot/stk/tru64_stk/impacts/i24.html However, they are not gone so I think we should define _REENTRANT if there are no ill effects. Dave
