Skip to content
Projects
Groups
Snippets
Help
This project
Loading...
Sign in / Register
Toggle navigation
R
riscv-gcc-1
Overview
Overview
Details
Activity
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Board
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Charts
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
lvzhengyang
riscv-gcc-1
Commits
7daa7b1d
Commit
7daa7b1d
authored
May 14, 2011
by
Janne Blomqvist
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
PR 48915 Update mixed-language programming documentation
From-SVN: r173753
parent
222c2a63
Show whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
13 additions
and
7 deletions
+13
-7
gcc/fortran/ChangeLog
+7
-0
gcc/fortran/gfortran.texi
+6
-7
No files found.
gcc/fortran/ChangeLog
View file @
7daa7b1d
2011-05-14 Janne Blomqvist <jb@gcc.gnu.org>
PR libfortran/48915
* gfortran.texi: Update mixed-language programming section
reflecting the removal of the fdump-core option, and that
-fbacktrace is now enabled by default.
2011-05-14 Thomas Koenig <tkoenig@gcc.gnu.org>
PR fortran/22572
...
...
gcc/fortran/gfortran.texi
View file @
7daa7b1d
...
...
@@ -2527,7 +2527,7 @@ gfortran calls @code{_gfortran_set_args} and
@code{_gfortran_set_options}. The initialization of the former
is needed if the called procedures access the command line
(and for backtracing); the latter sets some flags based on the
standard chosen or to
en
able backtracing. In typical programs,
standard chosen or to
dis
able backtracing. In typical programs,
it is not necessary to call any initialization function.
If your @code{PROGRAM} is compiled with GNU Fortran, you shall
...
...
@@ -2578,7 +2578,7 @@ int main (int argc, char *argv[])
@table @asis
@item @emph{Description}:
@code{_gfortran_set_options} sets several flags related to the Fortran
standard to be used, whether backtracing
or core dumps
should be enabled
standard to be used, whether backtracing should be enabled
and whether range checks should be performed. The syntax allows for
upward compatibility since the number of passed flags is specified; for
non-passed flags, the default value is used. See also
...
...
@@ -2609,10 +2609,9 @@ Possible values are (bitwise or-ed) @code{GFC_STD_F77} (1),
standard error. Default: @code{GFC_STD_F95_DEL | GFC_STD_LEGACY}.
@item @var{option}[2] @tab If non zero, enable pedantic checking.
Default: off.
@item @var{option}[3] @tab If non zero, enable core dumps on run-time
errors. Default: off.
@item @var{option}[3] @tab Unused.
@item @var{option}[4] @tab If non zero, enable backtracing on run-time
errors. Default:
off
.
errors. Default:
enabled
.
Note: Installs a signal handler and requires command-line
initialization using @code{_gfortran_set_args}.
@item @var{option}[5] @tab If non zero, supports signed zeros.
...
...
@@ -2627,8 +2626,8 @@ Default: enabled. See -frange-check (@pxref{Code Gen Options}).
@item @emph{Example}:
@smallexample
/* Use gfortran 4.
5
default options. */
static int options[] = @{68, 255, 0, 0,
0
, 1, 0, 1@};
/* Use gfortran 4.
7
default options. */
static int options[] = @{68, 255, 0, 0,
1
, 1, 0, 1@};
_gfortran_set_options (8, &options);
@end smallexample
@end table
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment