| All Forums |
Register |
Login |
Search |
Subscriptions |
My Profile |
Inbox |
| Tool Warehouse |
FAQs |
Resources |
Help |
Member List |
Address Book |
Logout |
|
|
gcc 3.2 PIC
|
Logged in as: Guest |
| Users viewing this topic: none |
|
Login  |
|
|
 gcc 3.2 PIC - Sep. 24, '02, 4:09:39 PM
|
|
|
Rodney
Posts: 3728
Joined: Jul. 9, '02,
From: /Tools lab
Status: offline
|
With gcc 3.2 I' ve noticed that there is a problem that sometimes happens when position independent code (PIC) is being made for shared libraries (" -fpic" ). The solution/work-around so far is the traditional " don' t do that then" . The problem seen is that the code wacks the stack and sets some registers to unexpected values. The problem doesn' t happen for all shared/PIC code. So " -fpic" may still work for some code and not others.
|
|
|
|
|
RE: gcc 3.2 PIC - Sep. 25, '02, 10:57:26 PM
|
|
|
Rodney
Posts: 3728
Joined: Jul. 9, '02,
From: /Tools lab
Status: offline
|
Just to be clear, you can still make shared libraries without using the " -fpic" option.
|
|
|
|
 New Messages |
 No New Messages |
 Hot Topic w/ New Messages |
 Hot Topic w/o New Messages |
|
 Locked w/ New Messages |
 Locked w/o New Messages |
|
 Post New Thread
Reply to Message
Post New Poll
Submit Vote
Delete My Own Post
Delete My Own Thread
Rate Posts |
|
|
|
Printable Version
