RFC: 8136978 Much nearly duplicated code for vmError support (original) (raw)
Kim Barrett kim.barrett at oracle.com
Tue Oct 13 21:03:50 UTC 2015
- Previous message: RFC: 8136978 Much nearly duplicated code for vmError support
- Next message: RFC: 8136978 Much nearly duplicated code for vmError support
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Oct 13, 2015, at 3:21 PM, Sebastian Sickelmann <sebastian.sickelmann at gmx.de> wrote:
But for ucontextsetpc and ucontextgetpc i see two variants: Implement in in os/[]/vm/os[].cpp like this: address os::Posix::ucontextgetpc(ucontextt* ctx) { return os::Linux::ucontextgetpc(ctx); } and call the existing methods from the oscpu directory. Or remove the ucontextgetpc and ucontextsetpc from the os/[]/vm/os[].hpp and change the implementations in oscpu//vm/os[][**].cpp from os::[*]::ucontext....... to os::Posix::ucontext......... I think the solutions are identically from the view of the compile result at least when inlining is used. I think the first solutions would creates a smaller changeset. I think the second solution would lead to a slightly smaller codebase. What do you think? I personally prefer the second.
I prefer the second as well, but you should get an opinion from someone on the runtime team, as they’re the folks who will end up maintaining the result.
Having multiple scattered os::Posix:: implementations would be consistent in style with the multiple scattered os:: implementations, but still a new thing to know about.
- Previous message: RFC: 8136978 Much nearly duplicated code for vmError support
- Next message: RFC: 8136978 Much nearly duplicated code for vmError support
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]