Bug 644 - executable file that compiled by "f77 -r8" makes core dump.
Summary: executable file that compiled by "f77 -r8" makes core dump.
Status: Closed FIXED
Alias: None
Product: Base System
Classification: Unclassified
Component: gnu (show other bugs)
Version: Unspecified
Hardware: Any Any
: Normal Affects Only Me
Assignee: freebsd-bugs (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 1995-07-31 20:30 UTC by Takeshi WATANABE
Modified: 1995-08-04 18:14 UTC (History)
0 users

See Also:

Attachments
file.diff (720 bytes, patch)
1995-07-31 20:30 UTC, Takeshi WATANABE 		no flags Details | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Takeshi WATANABE 1995-07-31 20:30:00 UTC 
  Executable file that compiled by "f77 -r8" makes core dump. ("f77"
without "-r8" option makes no problem)

	% f77 -r8 test.f
	% ./a.out
	Segmentation fault (core dumped)

# "-r8" is meaningful option for "f2c" command.  "f77" calls "f2c".

In spite of this, "f77 -c -r8" makes no problem.

	% f77 -c -r8 test.f
	% f77 test.o
	% ./a.out
(This is OK.)

  I tested "f77" command with "-v" option.  It was found that "f77" command
(without "-r8") calls finally "ld" command with "-e start" option.  However,
"f77 -r8" calls "ld" command without "-e start" option.

  I think that this feature is meaningful for "f77 -r".  However, it's
maybe meaningless for "f77 -r8".
  So, the condition for "-e start" option may change from "!r*" to "!r".

How-To-Repeat: 
  Always on FreeBSD-2.0(.5)-RELEASE.  Never on FreeBSD-1.1.5.1-RELEASE.
Comment 1 Joerg Wunsch freebsd_committer freebsd_triage 1995-08-04 18:12:03 UTC 
State Changed
From-To: open->closed

Suggested fix applied in rev 1.11 of cc/include/tm.h