search

atwhaley / cfast

Automatically exported from code.google.com/p/cfast
0 stars 2 forks source link

Does non PC CFAST need to worry about compiler directives in DREADIN #94

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Binary history file code in CFAST includes compiler directives that determine 
big-endian / little endian behavior (see DREADIN in input.f).  With the recent 
addition of linux / mac / ... build files, do we need to make sure this code is 
correct and/or can we carefully elimiate this code? See Issue #27.

Original issue reported on code.google.com by cfastdev@gmail.com on 1 Jun 2012 at 6:48

GoogleCodeExporter commented 9 years ago 
I'm guessing we don't need these directives.  All three platforms we have 
makefile entries for have the same endian properties.  we can talk about this 
more when I get back.

Original comment by gfor...@gmail.com on 2 Jun 2012 at 1:44

GoogleCodeExporter commented 9 years ago 
These should be gone now.

Original comment by cfastdev@gmail.com on 22 Jul 2013 at 2:09