-
Notifications
You must be signed in to change notification settings - Fork 59
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PAPI_ECMP and PAPI_ESBSTR Assigned Same Value #198
Comments
Files that contain
Files that contain
|
The following is mentioned (dated 2012-07-05) in Move uses of PAPI_ESBSTR to PAPI_ECMP I left PAPI_ESBSTR defined too for backward compatability. Also some of the changes update PAPI_ESBSTR to be a more relevant error code, it one is available. Comment seems to come from Tony. |
I guess I can weigh in here. As the comments say, this was done intentionally. Prior to PAPI 4.0 ("component PAPI") the various interfaces were called substrates and would return PAPI_ESBSTR. When things were modularized into components, it made sense to report these as PAPI_ECMP instead. However since these values are reported to the user it might in theory break user code if we just removed the PAPI_ESBSTR definition. So we left it there as an alias for PAPI_ECMP. Is this currently breaking things? Or is it just not documented well enough? The leftover PAPI_ESBSTR in the libpfm4 code is an overight and should probably be fixed |
@deater Thanks for more clarification on this. As stands this is not causing anything to break, but it was not clear initially when looking through From prior discussions with Heike, we decided to leave the I do agree that removing |
PAPI_ESBSTR
andPAPI_ECMP
both have the same value of -4 assigned to them, this can be seen in lines 258,259 inpapi.c
.This issue is being looked into further by the PAPI team.
The text was updated successfully, but these errors were encountered: