Skip to content
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

Broken on armv7: no member named '_gregs' in 'mcontext_t'; did you mean '__gregs'? #534

Closed
yurivict opened this issue Sep 9, 2022 · 2 comments

Comments

@yurivict
Copy link

yurivict commented Sep 9, 2022

/wrkdirs/usr/ports/cad/nvc/work/nvc-r1.7.1/thirdparty/cpustate.c:117:30: error: no member named '_gregs' in 'mcontext_t'; did you mean '__gregs'?
   cpu->pc = uc->uc_mcontext._gregs[_REG_PC];
                             ^~~~~~
                             __gregs
/usr/include/machine/ucontext.h:77:14: note: '__gregs' declared here
        __gregset_t     __gregs;
                        ^
/wrkdirs/usr/ports/cad/nvc/work/nvc-r1.7.1/thirdparty/cpustate.c:118:30: error: no member named '_gregs' in 'mcontext_t'; did you mean '__gregs'?
   cpu->sp = uc->uc_mcontext._gregs[_REG_SP];
                             ^~~~~~
                             __gregs
/usr/include/machine/ucontext.h:77:14: note: '__gregs' declared here
        __gregset_t     __gregs;
                        ^
/wrkdirs/usr/ports/cad/nvc/work/nvc-r1.7.1/thirdparty/cpustate.c:121:38: error: no member named '_gregs' in 'mcontext_t'; did you mean '__gregs'?
      cpu->regs[i] = uc->uc_mcontext._gregs[i];
                                     ^~~~~~
                                     __gregs
/usr/include/machine/ucontext.h:77:14: note: '__gregs' declared here
        __gregset_t     __gregs;
                        ^
3 errors generated.

Version: 1.7.1
FreeBSD 13.1

@nickg
Copy link
Owner

nickg commented Sep 19, 2022

Yes it's a simple typo, unfortunately I didn't have access to a FreeBSD/arm machine to test. I'll fix it for the 1.7.2 release.

@nickg
Copy link
Owner

nickg commented Oct 16, 2022

This is fixed in the 1.7.2 release.

@nickg nickg closed this as completed Oct 16, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants