The application characteristics for the instrumented object file with C program
up vote
0
down vote
favorite
Anyone could give me more practical explanation for the following instrumented object/code/execution concepts! https://www.sharcnet.ca/Software/Intel/IFC/compiler_f/main_for/copts/common_options/option_prof_gen.htm
Because under some circumstances, when remissly using an incorrect postfix of the source file, the linker would in turn take it for an instrumented object file to be (re-)processed by the compiler backend - that is the case when it tried to load libucomp.so.
For example:
#
# gcc scsi_sp -o scsi_exec
ld: 92453-07 linker ld HP Itanium(R) B.12.61 IPF/IPF
ld: Unable to load shared library /opt/langtools/lib/hpux64/libu2comp.so"
Fatal error. collect2: ld returned 1 exit status
#
Notes: apparently libu2comp.so is a library which is the optimized code generator for the compiler.
So, why a wrong postfix of the source file might be considered as an instrumented object file ?
c instrumentation
add a comment |
up vote
0
down vote
favorite
Anyone could give me more practical explanation for the following instrumented object/code/execution concepts! https://www.sharcnet.ca/Software/Intel/IFC/compiler_f/main_for/copts/common_options/option_prof_gen.htm
Because under some circumstances, when remissly using an incorrect postfix of the source file, the linker would in turn take it for an instrumented object file to be (re-)processed by the compiler backend - that is the case when it tried to load libucomp.so.
For example:
#
# gcc scsi_sp -o scsi_exec
ld: 92453-07 linker ld HP Itanium(R) B.12.61 IPF/IPF
ld: Unable to load shared library /opt/langtools/lib/hpux64/libu2comp.so"
Fatal error. collect2: ld returned 1 exit status
#
Notes: apparently libu2comp.so is a library which is the optimized code generator for the compiler.
So, why a wrong postfix of the source file might be considered as an instrumented object file ?
c instrumentation
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
Anyone could give me more practical explanation for the following instrumented object/code/execution concepts! https://www.sharcnet.ca/Software/Intel/IFC/compiler_f/main_for/copts/common_options/option_prof_gen.htm
Because under some circumstances, when remissly using an incorrect postfix of the source file, the linker would in turn take it for an instrumented object file to be (re-)processed by the compiler backend - that is the case when it tried to load libucomp.so.
For example:
#
# gcc scsi_sp -o scsi_exec
ld: 92453-07 linker ld HP Itanium(R) B.12.61 IPF/IPF
ld: Unable to load shared library /opt/langtools/lib/hpux64/libu2comp.so"
Fatal error. collect2: ld returned 1 exit status
#
Notes: apparently libu2comp.so is a library which is the optimized code generator for the compiler.
So, why a wrong postfix of the source file might be considered as an instrumented object file ?
c instrumentation
Anyone could give me more practical explanation for the following instrumented object/code/execution concepts! https://www.sharcnet.ca/Software/Intel/IFC/compiler_f/main_for/copts/common_options/option_prof_gen.htm
Because under some circumstances, when remissly using an incorrect postfix of the source file, the linker would in turn take it for an instrumented object file to be (re-)processed by the compiler backend - that is the case when it tried to load libucomp.so.
For example:
#
# gcc scsi_sp -o scsi_exec
ld: 92453-07 linker ld HP Itanium(R) B.12.61 IPF/IPF
ld: Unable to load shared library /opt/langtools/lib/hpux64/libu2comp.so"
Fatal error. collect2: ld returned 1 exit status
#
Notes: apparently libu2comp.so is a library which is the optimized code generator for the compiler.
So, why a wrong postfix of the source file might be considered as an instrumented object file ?
c instrumentation
c instrumentation
asked Nov 12 at 3:16
lylklb
1215
1215
add a comment |
add a comment |
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function ()
StackExchange.using("externalEditor", function ()
StackExchange.using("snippets", function ()
StackExchange.snippets.init();
);
);
, "code-snippets");
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "1"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53255537%2fthe-application-characteristics-for-the-instrumented-object-file-with-c-program%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53255537%2fthe-application-characteristics-for-the-instrumented-object-file-with-c-program%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown