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
a9cd52eb
Commit
a9cd52eb
authored
Mar 13, 1995
by
Jason Merrill
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Use -fPIC instead of -fpic
From-SVN: r9178
parent
0f07e76c
Hide whitespace changes
Inline
Side-by-side
Showing
4 changed files
with
12 additions
and
12 deletions
+12
-12
gcc/config/i386/t-crtpic
+3
-3
gcc/config/i386/t-sol2
+3
-3
gcc/config/sparc/t-sol2
+3
-3
gcc/config/t-svr4
+3
-3
No files found.
gcc/config/i386/t-crtpic
View file @
a9cd52eb
# The pushl in CTOR initialization interferes with frame pointer elimination.
# We need to use -f
pic
when we are using gcc to compile the routines in
# We need to use -f
PIC
when we are using gcc to compile the routines in
# crtstuff.c. This is only really needed when we are going to use gcc/g++
# to produce a shared library, but since we don't know ahead of time when
# we will be doing that, we just always use -f
pic
when compiling the
# we will be doing that, we just always use -f
PIC
when compiling the
# routines in crtstuff.c.
CRTSTUFF_T_CFLAGS = -f
pic
-fno-omit-frame-pointer
CRTSTUFF_T_CFLAGS = -f
PIC
-fno-omit-frame-pointer
gcc/config/i386/t-sol2
View file @
a9cd52eb
...
...
@@ -23,10 +23,10 @@ crtn.o: $(srcdir)/config/i386/sol2-cn.asm
sed -e '/^!/d' <$(srcdir)/config/i386/sol2-cn.asm >crtn.s
$(AS) -o crtn.o crtn.s
# We need to use -f
pic
when we are using gcc to compile the routines in
# We need to use -f
PIC
when we are using gcc to compile the routines in
# crtstuff.c. This is only really needed when we are going to use gcc/g++
# to produce a shared library, but since we don't know ahead of time when
# we will be doing that, we just always use -f
pic
when compiling the
# we will be doing that, we just always use -f
PIC
when compiling the
# routines in crtstuff.c.
CRTSTUFF_T_CFLAGS = -f
pic
CRTSTUFF_T_CFLAGS = -f
PIC
gcc/config/sparc/t-sol2
View file @
a9cd52eb
...
...
@@ -17,14 +17,14 @@ crti.o: $(srcdir)/config/sparc/sol2-ci.asm
crtn.o: $(srcdir)/config/sparc/sol2-cn.asm
$(AS) -o crtn.o $(srcdir)/config/sparc/sol2-cn.asm
# We need to use -f
pic
when we are using gcc to compile the routines in
# We need to use -f
PIC
when we are using gcc to compile the routines in
# crtstuff.c. This is only really needed when we are going to use gcc/g++
# to produce a shared library, but since we don't know ahead of time when
# we will be doing that, we just always use -f
pic
when compiling the
# we will be doing that, we just always use -f
PIC
when compiling the
# routines in crtstuff.c.
# Since the GNU assembler doesn't support PIC yet, we need to force gcc to
# use the native assembler when building crtstuff. If we're a
# cross-compiler, just give up on using PIC.
CRTSTUFF_T_CFLAGS = `if [ -z "$(CROSS)" ]; then echo -f
pic
-B/usr/ccs/bin/; fi`
CRTSTUFF_T_CFLAGS = `if [ -z "$(CROSS)" ]; then echo -f
PIC
-B/usr/ccs/bin/; fi`
gcc/config/t-svr4
View file @
a9cd52eb
# We need to use -f
pic
when we are using gcc to compile the routines in
# We need to use -f
PIC
when we are using gcc to compile the routines in
# crtstuff.c. This is only really needed when we are going to use gcc/g++
# to produce a shared library, but since we don't know ahead of time when
# we will be doing that, we just always use -f
pic
when compiling the
# we will be doing that, we just always use -f
PIC
when compiling the
# routines in crtstuff.c.
CRTSTUFF_T_CFLAGS = -f
pic
CRTSTUFF_T_CFLAGS = -f
PIC
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