Fortran's findloc with character type
Multi tool use
I'm confused by the findloc intrinsic with a character array.
The program
print *, findloc(['AB'],'A',dim=1)
end
outputs
1
while I expected 0.
I thought that findloc searched for equality, and 'A' /= 'AB'.
If I make the scalar value of equal type as the array, then I do get what I expected: findloc(['AB'],'A ',dim=1) gives 0.
Note that findloc(['BA'],'A',dim=1) does give 0, so I don't think that findloc uses the index function.
I'm using ifort 18.0.3 on centos 7.
fortran intel-fortran
asked Jan 18 at 17:27
A. HenninkA. Hennink
121111
add a comment |
I'm confused by the findloc intrinsic with a character array.
The program
print *, findloc(['AB'],'A',dim=1)
end
outputs
1
while I expected 0.
I thought that findloc searched for equality, and 'A' /= 'AB'.
If I make the scalar value of equal type as the array, then I do get what I expected: findloc(['AB'],'A ',dim=1) gives 0.
Note that findloc(['BA'],'A',dim=1) does give 0, so I don't think that findloc uses the index function.
I'm using ifort 18.0.3 on centos 7.
fortran intel-fortran
asked Jan 18 at 17:27
A. HenninkA. Hennink
121111
Yes, I usedifort -O0 -stand f08 -warn all -check all. Andfindlocis Fortran 2008, so I'd be surprised if their implementation is old. Besides, I thought that this behavior would be standardized.
– A. Hennink
Jan 18 at 17:45
Can you try with 19.0.1?
– francescalus
Jan 18 at 17:55
No, unfortunately not. And my version ofgfortranis way too old.
– A. Hennink
Jan 18 at 17:57
2
Its just a compiler bug. You can report such things at supporttickets.intel.com.
– IanH
Jan 18 at 21:19
2
@francescalus I tested this with Intel Fortran Compiler 2019, and the bug persists.
– King
Jan 20 at 0:03
add a comment |
I'm confused by the findloc intrinsic with a character array.
The program
print *, findloc(['AB'],'A',dim=1)
end
outputs
1
while I expected 0.
I thought that findloc searched for equality, and 'A' /= 'AB'.
If I make the scalar value of equal type as the array, then I do get what I expected: findloc(['AB'],'A ',dim=1) gives 0.
Note that findloc(['BA'],'A',dim=1) does give 0, so I don't think that findloc uses the index function.
I'm using ifort 18.0.3 on centos 7.
fortran intel-fortran
asked Jan 18 at 17:27
A. HenninkA. Hennink
121111
I'm confused by the findloc intrinsic with a character array.
The program
print *, findloc(['AB'],'A',dim=1)
end
outputs
1
while I expected 0.
I thought that findloc searched for equality, and 'A' /= 'AB'.
If I make the scalar value of equal type as the array, then I do get what I expected: findloc(['AB'],'A ',dim=1) gives 0.
Note that findloc(['BA'],'A',dim=1) does give 0, so I don't think that findloc uses the index function.
I'm using ifort 18.0.3 on centos 7.
fortran intel-fortran
fortran intel-fortran
asked Jan 18 at 17:27
A. HenninkA. Hennink
121111
asked Jan 18 at 17:27
A. HenninkA. Hennink
121111
edited Jan 18 at 17:47
A. Hennink
asked Jan 18 at 17:27
A. HenninkA. Hennink
121111
asked Jan 18 at 17:27
A. HenninkA. Hennink
121111
asked Jan 18 at 17:27
A. HenninkA. Hennink
121111
121111
Yes, I usedifort -O0 -stand f08 -warn all -check all. Andfindlocis Fortran 2008, so I'd be surprised if their implementation is old. Besides, I thought that this behavior would be standardized.
– A. Hennink
Jan 18 at 17:45
Can you try with 19.0.1?
– francescalus
Jan 18 at 17:55
No, unfortunately not. And my version ofgfortranis way too old.
– A. Hennink
Jan 18 at 17:57
2
Its just a compiler bug. You can report such things at supporttickets.intel.com.
– IanH
Jan 18 at 21:19
2
@francescalus I tested this with Intel Fortran Compiler 2019, and the bug persists.
– King
Jan 20 at 0:03
add a comment |
Yes, I usedifort -O0 -stand f08 -warn all -check all. Andfindlocis Fortran 2008, so I'd be surprised if their implementation is old. Besides, I thought that this behavior would be standardized.
– A. Hennink
Jan 18 at 17:45
Can you try with 19.0.1?
– francescalus
Jan 18 at 17:55
No, unfortunately not. And my version ofgfortranis way too old.
– A. Hennink
Jan 18 at 17:57
2
Its just a compiler bug. You can report such things at supporttickets.intel.com.
– IanH
Jan 18 at 21:19
2
@francescalus I tested this with Intel Fortran Compiler 2019, and the bug persists.
– King
Jan 20 at 0:03
Yes, I used
ifort -O0 -stand f08 -warn all -check all. And findloc is Fortran 2008, so I'd be surprised if their implementation is old. Besides, I thought that this behavior would be standardized.– A. Hennink
Jan 18 at 17:45
Yes, I used
ifort -O0 -stand f08 -warn all -check all. And findloc is Fortran 2008, so I'd be surprised if their implementation is old. Besides, I thought that this behavior would be standardized.– A. Hennink
Jan 18 at 17:45
Can you try with 19.0.1?
– francescalus
Jan 18 at 17:55
Can you try with 19.0.1?
– francescalus
Jan 18 at 17:55
No, unfortunately not. And my version of
gfortran is way too old.– A. Hennink
Jan 18 at 17:57
No, unfortunately not. And my version of
gfortran is way too old.– A. Hennink
Jan 18 at 17:57
2
2
Its just a compiler bug. You can report such things at supporttickets.intel.com.
– IanH
Jan 18 at 21:19
Its just a compiler bug. You can report such things at supporttickets.intel.com.
– IanH
Jan 18 at 21:19
2
2
@francescalus I tested this with Intel Fortran Compiler 2019, and the bug persists.
– King
Jan 20 at 0:03
@francescalus I tested this with Intel Fortran Compiler 2019, and the bug persists.
– King
Jan 20 at 0:03
add a comment |
1 Answer
1
active
oldest
votes
I agree that this is a bug in Intel Fortran's findloc() implementation. I created an Intel bug report to our developers.
answered 2 days ago
R. GreenR. Green
461
New contributor
R. Green is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
So it's possible to write a 28-byte full program that triggers a bug:print*,findloc(['A'],'');end. That must be some sort of record. But these things happen, and Fortran's characters are probably not the easiest to deal with. Thank you for letting us know.
– A. Hennink
yesterday
add a comment |
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%2f54258795%2ffortrans-findloc-with-character-type%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
I agree that this is a bug in Intel Fortran's findloc() implementation. I created an Intel bug report to our developers.
answered 2 days ago
R. GreenR. Green
461
New contributor
R. Green is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
So it's possible to write a 28-byte full program that triggers a bug:print*,findloc(['A'],'');end. That must be some sort of record. But these things happen, and Fortran's characters are probably not the easiest to deal with. Thank you for letting us know.
– A. Hennink
yesterday
add a comment |
I agree that this is a bug in Intel Fortran's findloc() implementation. I created an Intel bug report to our developers.
answered 2 days ago
R. GreenR. Green
461
New contributor
R. Green is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
So it's possible to write a 28-byte full program that triggers a bug:print*,findloc(['A'],'');end. That must be some sort of record. But these things happen, and Fortran's characters are probably not the easiest to deal with. Thank you for letting us know.
– A. Hennink
yesterday
add a comment |
I agree that this is a bug in Intel Fortran's findloc() implementation. I created an Intel bug report to our developers.
answered 2 days ago
R. GreenR. Green
461
New contributor
R. Green is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
I agree that this is a bug in Intel Fortran's findloc() implementation. I created an Intel bug report to our developers.
answered 2 days ago
R. GreenR. Green
461
New contributor
R. Green is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered 2 days ago
R. GreenR. Green
461
New contributor
R. Green is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered 2 days ago
R. GreenR. Green
461
answered 2 days ago
R. GreenR. Green
461
461
New contributor
R. Green is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
R. Green is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
R. Green is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
So it's possible to write a 28-byte full program that triggers a bug:print*,findloc(['A'],'');end. That must be some sort of record. But these things happen, and Fortran's characters are probably not the easiest to deal with. Thank you for letting us know.
– A. Hennink
yesterday
add a comment |
So it's possible to write a 28-byte full program that triggers a bug:print*,findloc(['A'],'');end. That must be some sort of record. But these things happen, and Fortran's characters are probably not the easiest to deal with. Thank you for letting us know.
– A. Hennink
yesterday
So it's possible to write a 28-byte full program that triggers a bug:
print*,findloc(['A'],'');end. That must be some sort of record. But these things happen, and Fortran's characters are probably not the easiest to deal with. Thank you for letting us know.– A. Hennink
yesterday
So it's possible to write a 28-byte full program that triggers a bug:
print*,findloc(['A'],'');end. That must be some sort of record. But these things happen, and Fortran's characters are probably not the easiest to deal with. Thank you for letting us know.– A. Hennink
yesterday
add a comment |
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.
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%2f54258795%2ffortrans-findloc-with-character-type%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
lu eXwspv8cl3trp 6Ip,E8OzzAp2NmrTulAShvD op4TeN0V9Eilbpis3bzCTVVIaZ
Yes, I used
ifort -O0 -stand f08 -warn all -check all. Andfindlocis Fortran 2008, so I'd be surprised if their implementation is old. Besides, I thought that this behavior would be standardized.– A. Hennink
Jan 18 at 17:45
Can you try with 19.0.1?
– francescalus
Jan 18 at 17:55
No, unfortunately not. And my version of
gfortranis way too old.– A. Hennink
Jan 18 at 17:57
2
Its just a compiler bug. You can report such things at supporttickets.intel.com.
– IanH
Jan 18 at 21:19
2
@francescalus I tested this with Intel Fortran Compiler 2019, and the bug persists.
– King
Jan 20 at 0:03