Is it possible to get a pointer to one subobject via a pointer to a different, unreleated subobject?Where in the C++ Standard is the memory layout of objects documented?What are the differences between a pointer variable and a reference variable in C++?Is the Empty Base Class Optimization now a mandatory optimization (at least for standard-layout classes)?Pointer arithmetic across subobject boundariesWhy is f(i = -1, i = -1) undefined behavior?What makes it possible for glibc malloc to compare pointers from different “objects”?Can an equality comparison of unrelated pointers evaluate to true?Compatibility between structs with differently const-qualified pointersGuaranteed memory layout for standard layout struct with a single array member of primitive typeUsing std::launder to get a pointer to an active union member from a pointer to an inactive union member?Accessing the members of a struct referenced by a void pointer

Make Interviewee Comfortable in Potentially Intimate Environment

What are sources for Magic Items that are not adventure-specific?

What is the word for a person who destroys monuments?

Weapon class firing logic in JavaScript

Tips for remembering the order of parameters for ln?

Lead Amalgam as a Material for a Sword

What can I actually do with a high credit score?

How should errors be reported in scientific libraries?

Why are Fuji lenses more expensive than others?

What is the maximum viable speed for a projectile within earth's atmosphere?

Is there a connection between IT and Ghostbusters?

Why is it called a Blood Knot?

Paradox regarding phase transitions in relativistic systems

Does battery condition have anything to do with macbook pro performance?

How to ask a man to not take up more than one seat on public transport while avoiding conflict?

Why would a fighter use the afterburner and air brakes at the same time?

Is “卧草” a proper Chinese word?

What is the origin of the "being immortal sucks" trope?

Who are the people reviewing far more papers than they're submitting for review?

I feel like most of my characters are the same, what can I do?

Incorrect syntax near '+' in stored procedure sql server

How is underwater propagation of sound possible?

Which museums have artworks of all four ninja turtles' namesakes?

All numbers in a 5x5 Minesweeper grid



Is it possible to get a pointer to one subobject via a pointer to a different, unreleated subobject?


Where in the C++ Standard is the memory layout of objects documented?What are the differences between a pointer variable and a reference variable in C++?Is the Empty Base Class Optimization now a mandatory optimization (at least for standard-layout classes)?Pointer arithmetic across subobject boundariesWhy is f(i = -1, i = -1) undefined behavior?What makes it possible for glibc malloc to compare pointers from different “objects”?Can an equality comparison of unrelated pointers evaluate to true?Compatibility between structs with differently const-qualified pointersGuaranteed memory layout for standard layout struct with a single array member of primitive typeUsing std::launder to get a pointer to an active union member from a pointer to an inactive union member?Accessing the members of a struct referenced by a void pointer






.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;








11















Look at this simple code:



struct Point 
 int x;
 int y;
;

void something(int *);

int main() 
 Point p1, 2;

 something(&p.x);

 return p.y;



I expect, that main's return value can be optimized to return 2;, as something doesn't have access to p.y, it only gets a pointer to p.x.



But, none of the major compilers optimize the return value of main to 2. Godbolt.



Is there something in the standard, which allows something to modify p.y, if we only give access to p.x? If yes, does this depend on whether Point has standard layout?



What if I use something(&p.y);, and return p.x; instead?






c++ language-lawyer c++17







share|improve this question





















  • 1





    I don't understand the downvote and the flag. This is perfectly reasonable question to me.

    – Zereges
    8 hours ago











  • stackoverflow.com/questions/50803202/… "Implementation alignment requirements might cause two adjacent members not to be allocated immediately after each other"

    – alter igel
    8 hours ago











  • @alterigel: this shouldn't matter, as we can use offsetof. But I'm not sure that we can actually get a pointer to p.y from p.x, with the new pointer semantic rules of C++17. std::launder cannot be used, as a pointer to p.x can only reach p.x. So even if I could move the pointer to the correct location, maybe that pointer won't point to the object of p.y.

    – geza
    8 hours ago












  • If you change it to void something(int * x) *(x+1) = 6; it optimizes the return value to a fixed 6, so the compiler at least sees that as a valid option to do.

    – t.niese
    8 hours ago






  • 1





    @zereges, didn't downvote, but almost did. The question is very hard to parse. I believe the OP is asking: "why can't the compiler realize the something() function will not modify p.y ?" If the OP asked that directly, there'd be less downvotes.

    – Jeffrey
    8 hours ago


















11















Look at this simple code:



struct Point 
 int x;
 int y;
;

void something(int *);

int main() 
 Point p1, 2;

 something(&p.x);

 return p.y;



I expect, that main's return value can be optimized to return 2;, as something doesn't have access to p.y, it only gets a pointer to p.x.



But, none of the major compilers optimize the return value of main to 2. Godbolt.



Is there something in the standard, which allows something to modify p.y, if we only give access to p.x? If yes, does this depend on whether Point has standard layout?



What if I use something(&p.y);, and return p.x; instead?






c++ language-lawyer c++17







share|improve this question





















  • 1





    I don't understand the downvote and the flag. This is perfectly reasonable question to me.

    – Zereges
    8 hours ago











  • stackoverflow.com/questions/50803202/… "Implementation alignment requirements might cause two adjacent members not to be allocated immediately after each other"

    – alter igel
    8 hours ago











  • @alterigel: this shouldn't matter, as we can use offsetof. But I'm not sure that we can actually get a pointer to p.y from p.x, with the new pointer semantic rules of C++17. std::launder cannot be used, as a pointer to p.x can only reach p.x. So even if I could move the pointer to the correct location, maybe that pointer won't point to the object of p.y.

    – geza
    8 hours ago












  • If you change it to void something(int * x) *(x+1) = 6; it optimizes the return value to a fixed 6, so the compiler at least sees that as a valid option to do.

    – t.niese
    8 hours ago






  • 1





    @zereges, didn't downvote, but almost did. The question is very hard to parse. I believe the OP is asking: "why can't the compiler realize the something() function will not modify p.y ?" If the OP asked that directly, there'd be less downvotes.

    – Jeffrey
    8 hours ago














11












11








11


1






Look at this simple code:



struct Point 
 int x;
 int y;
;

void something(int *);

int main() 
 Point p1, 2;

 something(&p.x);

 return p.y;



I expect, that main's return value can be optimized to return 2;, as something doesn't have access to p.y, it only gets a pointer to p.x.



But, none of the major compilers optimize the return value of main to 2. Godbolt.



Is there something in the standard, which allows something to modify p.y, if we only give access to p.x? If yes, does this depend on whether Point has standard layout?



What if I use something(&p.y);, and return p.x; instead?






c++ language-lawyer c++17







share|improve this question
















Look at this simple code:



struct Point 
 int x;
 int y;
;

void something(int *);

int main() 
 Point p1, 2;

 something(&p.x);

 return p.y;



I expect, that main's return value can be optimized to return 2;, as something doesn't have access to p.y, it only gets a pointer to p.x.



But, none of the major compilers optimize the return value of main to 2. Godbolt.



Is there something in the standard, which allows something to modify p.y, if we only give access to p.x? If yes, does this depend on whether Point has standard layout?



What if I use something(&p.y);, and return p.x; instead?






c++ language-lawyer c++17




c++ language-lawyer c++17






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited 8 hours ago







geza

















asked 8 hours ago









gezageza

16.6k3 gold badges40 silver badges97 bronze badges




16.6k3 gold badges40 silver badges97 bronze badges










  • 1





    I don't understand the downvote and the flag. This is perfectly reasonable question to me.

    – Zereges
    8 hours ago











  • stackoverflow.com/questions/50803202/… "Implementation alignment requirements might cause two adjacent members not to be allocated immediately after each other"

    – alter igel
    8 hours ago











  • @alterigel: this shouldn't matter, as we can use offsetof. But I'm not sure that we can actually get a pointer to p.y from p.x, with the new pointer semantic rules of C++17. std::launder cannot be used, as a pointer to p.x can only reach p.x. So even if I could move the pointer to the correct location, maybe that pointer won't point to the object of p.y.

    – geza
    8 hours ago












  • If you change it to void something(int * x) *(x+1) = 6; it optimizes the return value to a fixed 6, so the compiler at least sees that as a valid option to do.

    – t.niese
    8 hours ago






  • 1





    @zereges, didn't downvote, but almost did. The question is very hard to parse. I believe the OP is asking: "why can't the compiler realize the something() function will not modify p.y ?" If the OP asked that directly, there'd be less downvotes.

    – Jeffrey
    8 hours ago













  • 1





    I don't understand the downvote and the flag. This is perfectly reasonable question to me.

    – Zereges
    8 hours ago











  • stackoverflow.com/questions/50803202/… "Implementation alignment requirements might cause two adjacent members not to be allocated immediately after each other"

    – alter igel
    8 hours ago











  • @alterigel: this shouldn't matter, as we can use offsetof. But I'm not sure that we can actually get a pointer to p.y from p.x, with the new pointer semantic rules of C++17. std::launder cannot be used, as a pointer to p.x can only reach p.x. So even if I could move the pointer to the correct location, maybe that pointer won't point to the object of p.y.

    – geza
    8 hours ago












  • If you change it to void something(int * x) *(x+1) = 6; it optimizes the return value to a fixed 6, so the compiler at least sees that as a valid option to do.

    – t.niese
    8 hours ago






  • 1





    @zereges, didn't downvote, but almost did. The question is very hard to parse. I believe the OP is asking: "why can't the compiler realize the something() function will not modify p.y ?" If the OP asked that directly, there'd be less downvotes.

    – Jeffrey
    8 hours ago








1




1





I don't understand the downvote and the flag. This is perfectly reasonable question to me.

– Zereges
8 hours ago





I don't understand the downvote and the flag. This is perfectly reasonable question to me.

– Zereges
8 hours ago













stackoverflow.com/questions/50803202/… "Implementation alignment requirements might cause two adjacent members not to be allocated immediately after each other"

– alter igel
8 hours ago





stackoverflow.com/questions/50803202/… "Implementation alignment requirements might cause two adjacent members not to be allocated immediately after each other"

– alter igel
8 hours ago













@alterigel: this shouldn't matter, as we can use offsetof. But I'm not sure that we can actually get a pointer to p.y from p.x, with the new pointer semantic rules of C++17. std::launder cannot be used, as a pointer to p.x can only reach p.x. So even if I could move the pointer to the correct location, maybe that pointer won't point to the object of p.y.

– geza
8 hours ago






@alterigel: this shouldn't matter, as we can use offsetof. But I'm not sure that we can actually get a pointer to p.y from p.x, with the new pointer semantic rules of C++17. std::launder cannot be used, as a pointer to p.x can only reach p.x. So even if I could move the pointer to the correct location, maybe that pointer won't point to the object of p.y.

– geza
8 hours ago














If you change it to void something(int * x) *(x+1) = 6; it optimizes the return value to a fixed 6, so the compiler at least sees that as a valid option to do.

– t.niese
8 hours ago





If you change it to void something(int * x) *(x+1) = 6; it optimizes the return value to a fixed 6, so the compiler at least sees that as a valid option to do.

– t.niese
8 hours ago




1




1





@zereges, didn't downvote, but almost did. The question is very hard to parse. I believe the OP is asking: "why can't the compiler realize the something() function will not modify p.y ?" If the OP asked that directly, there'd be less downvotes.

– Jeffrey
8 hours ago






@zereges, didn't downvote, but almost did. The question is very hard to parse. I believe the OP is asking: "why can't the compiler realize the something() function will not modify p.y ?" If the OP asked that directly, there'd be less downvotes.

– Jeffrey
8 hours ago













2 Answers
2






active

oldest

votes


















13
















This is perfectly well-defined:



void something(int *x) 
 reinterpret_cast<Point*>(x)->y = 42;



The Point object (p) and its x member are pointer-interconvertible, from [basic.compound]:




Two objects a and b are pointer-interconvertible if:



  • [...]

  • one is a standard-layout class object and the other is the first non-static data member of that object, or, if the object has no non-static data members, any base class subobject of that object ([class.mem]), or:

  • [...]

If two objects are pointer-interconvertible, then they have the same address, and it is possible to obtain a pointer to one from a pointer to the other via a reinterpret_­cast.




That reinterpret_cast<Point*>(x) is valid and does end up with a pointer that points to p. Hence, modifying it directly is fine. As you can see, the standard-layout part and the first non-static data member part are significant.



Although it's not like the compilers in question optimize out the extra load if you pass a pointer to p.y in and return p.x instead.






share|improve this answer






















  • 1





    Thanks, I knew that I left a hole in my question. So, if I used something(&p.y); return p.x;, then it is clearly a missed optimization?

    – geza
    8 hours ago











  • @geza For some definition of "clearly". There almost certainly exists a lot of code that does things like this that such an optimization would break.

    – Barry
    7 hours ago






  • 1





    @geza Technically, yes, it would be a missed optimization then, but I don't think major compilers, at this time, are prepared to break all the existing code that uses offsetof.

    – Brian
    7 hours ago











  • Doesn't that violate the strict-aliasing rule? Or is that a C-only rule?

    – sturcotte06
    7 hours ago







  • 1





    @sturcotte06 it does not because of If two objects are pointer-interconvertible, then they have the same address, and it is possible to obtain a pointer to one from a pointer to the other via a reinterpret_­cast.

    – NathanOliver
    7 hours ago


















-4
















Given a POD structure (trivial with a standard layout, such as Point), you could change y as follows, even if x was not the first field in the object:



void something(int *data)

 data[(offsetof(Point, y)- offsetof(Point, x))/sizeof(int)] = 3;






share|improve this answer



























  • You might want to reread the question. The OP is not asking about this.

    – NathanOliver
    7 hours ago











  • The OP says Is there something in the standard, which allows something to modify p.y, if we only give access to p.x?

    – Gonen I
    7 hours ago











  • Correct. You are talking about an array, not whether or not something could modify y given a pointer to x.

    – NathanOliver
    7 hours ago











  • The result will be the same. It is not possible for the compiler to optimize, as the data is freely changeable by something given its prototype.

    – Gonen I
    7 hours ago











  • Sure, but arrays are different than structs and you cannot treat a pointer to a member as a pointer to an array. You also don't back up you claim with any text from the standard.

    – NathanOliver
    7 hours ago













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/4.0/"u003ecc by-sa 4.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
);



);














draft saved

draft discarded
















StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f57979009%2fis-it-possible-to-get-a-pointer-to-one-subobject-via-a-pointer-to-a-different-u%23new-answer', 'question_page');

);

Post as a guest















Required, but never shown

























2 Answers
2






active

oldest

votes








2 Answers
2






active

oldest

votes









active

oldest

votes






active

oldest

votes









13
















This is perfectly well-defined:



void something(int *x) 
 reinterpret_cast<Point*>(x)->y = 42;



The Point object (p) and its x member are pointer-interconvertible, from [basic.compound]:




Two objects a and b are pointer-interconvertible if:



  • [...]

  • one is a standard-layout class object and the other is the first non-static data member of that object, or, if the object has no non-static data members, any base class subobject of that object ([class.mem]), or:

  • [...]

If two objects are pointer-interconvertible, then they have the same address, and it is possible to obtain a pointer to one from a pointer to the other via a reinterpret_­cast.




That reinterpret_cast<Point*>(x) is valid and does end up with a pointer that points to p. Hence, modifying it directly is fine. As you can see, the standard-layout part and the first non-static data member part are significant.



Although it's not like the compilers in question optimize out the extra load if you pass a pointer to p.y in and return p.x instead.






share|improve this answer






















  • 1





    Thanks, I knew that I left a hole in my question. So, if I used something(&p.y); return p.x;, then it is clearly a missed optimization?

    – geza
    8 hours ago











  • @geza For some definition of "clearly". There almost certainly exists a lot of code that does things like this that such an optimization would break.

    – Barry
    7 hours ago






  • 1





    @geza Technically, yes, it would be a missed optimization then, but I don't think major compilers, at this time, are prepared to break all the existing code that uses offsetof.

    – Brian
    7 hours ago











  • Doesn't that violate the strict-aliasing rule? Or is that a C-only rule?

    – sturcotte06
    7 hours ago







  • 1





    @sturcotte06 it does not because of If two objects are pointer-interconvertible, then they have the same address, and it is possible to obtain a pointer to one from a pointer to the other via a reinterpret_­cast.

    – NathanOliver
    7 hours ago















13
















This is perfectly well-defined:



void something(int *x) 
 reinterpret_cast<Point*>(x)->y = 42;



The Point object (p) and its x member are pointer-interconvertible, from [basic.compound]:




Two objects a and b are pointer-interconvertible if:



  • [...]

  • one is a standard-layout class object and the other is the first non-static data member of that object, or, if the object has no non-static data members, any base class subobject of that object ([class.mem]), or:

  • [...]

If two objects are pointer-interconvertible, then they have the same address, and it is possible to obtain a pointer to one from a pointer to the other via a reinterpret_­cast.




That reinterpret_cast<Point*>(x) is valid and does end up with a pointer that points to p. Hence, modifying it directly is fine. As you can see, the standard-layout part and the first non-static data member part are significant.



Although it's not like the compilers in question optimize out the extra load if you pass a pointer to p.y in and return p.x instead.






share|improve this answer






















  • 1





    Thanks, I knew that I left a hole in my question. So, if I used something(&p.y); return p.x;, then it is clearly a missed optimization?

    – geza
    8 hours ago











  • @geza For some definition of "clearly". There almost certainly exists a lot of code that does things like this that such an optimization would break.

    – Barry
    7 hours ago






  • 1





    @geza Technically, yes, it would be a missed optimization then, but I don't think major compilers, at this time, are prepared to break all the existing code that uses offsetof.

    – Brian
    7 hours ago











  • Doesn't that violate the strict-aliasing rule? Or is that a C-only rule?

    – sturcotte06
    7 hours ago







  • 1





    @sturcotte06 it does not because of If two objects are pointer-interconvertible, then they have the same address, and it is possible to obtain a pointer to one from a pointer to the other via a reinterpret_­cast.

    – NathanOliver
    7 hours ago













13














13










13









This is perfectly well-defined:



void something(int *x) 
 reinterpret_cast<Point*>(x)->y = 42;



The Point object (p) and its x member are pointer-interconvertible, from [basic.compound]:




Two objects a and b are pointer-interconvertible if:



  • [...]

  • one is a standard-layout class object and the other is the first non-static data member of that object, or, if the object has no non-static data members, any base class subobject of that object ([class.mem]), or:

  • [...]

If two objects are pointer-interconvertible, then they have the same address, and it is possible to obtain a pointer to one from a pointer to the other via a reinterpret_­cast.




That reinterpret_cast<Point*>(x) is valid and does end up with a pointer that points to p. Hence, modifying it directly is fine. As you can see, the standard-layout part and the first non-static data member part are significant.



Although it's not like the compilers in question optimize out the extra load if you pass a pointer to p.y in and return p.x instead.






share|improve this answer















This is perfectly well-defined:



void something(int *x) 
 reinterpret_cast<Point*>(x)->y = 42;



The Point object (p) and its x member are pointer-interconvertible, from [basic.compound]:




Two objects a and b are pointer-interconvertible if:



  • [...]

  • one is a standard-layout class object and the other is the first non-static data member of that object, or, if the object has no non-static data members, any base class subobject of that object ([class.mem]), or:

  • [...]

If two objects are pointer-interconvertible, then they have the same address, and it is possible to obtain a pointer to one from a pointer to the other via a reinterpret_­cast.




That reinterpret_cast<Point*>(x) is valid and does end up with a pointer that points to p. Hence, modifying it directly is fine. As you can see, the standard-layout part and the first non-static data member part are significant.



Although it's not like the compilers in question optimize out the extra load if you pass a pointer to p.y in and return p.x instead.







share|improve this answer














share|improve this answer



share|improve this answer








edited 7 hours ago









T.C.

111k14 gold badges229 silver badges338 bronze badges




111k14 gold badges229 silver badges338 bronze badges










answered 8 hours ago









BarryBarry

200k22 gold badges373 silver badges665 bronze badges




200k22 gold badges373 silver badges665 bronze badges










  • 1





    Thanks, I knew that I left a hole in my question. So, if I used something(&p.y); return p.x;, then it is clearly a missed optimization?

    – geza
    8 hours ago











  • @geza For some definition of "clearly". There almost certainly exists a lot of code that does things like this that such an optimization would break.

    – Barry
    7 hours ago






  • 1





    @geza Technically, yes, it would be a missed optimization then, but I don't think major compilers, at this time, are prepared to break all the existing code that uses offsetof.

    – Brian
    7 hours ago











  • Doesn't that violate the strict-aliasing rule? Or is that a C-only rule?

    – sturcotte06
    7 hours ago







  • 1





    @sturcotte06 it does not because of If two objects are pointer-interconvertible, then they have the same address, and it is possible to obtain a pointer to one from a pointer to the other via a reinterpret_­cast.

    – NathanOliver
    7 hours ago












  • 1





    Thanks, I knew that I left a hole in my question. So, if I used something(&p.y); return p.x;, then it is clearly a missed optimization?

    – geza
    8 hours ago











  • @geza For some definition of "clearly". There almost certainly exists a lot of code that does things like this that such an optimization would break.

    – Barry
    7 hours ago






  • 1





    @geza Technically, yes, it would be a missed optimization then, but I don't think major compilers, at this time, are prepared to break all the existing code that uses offsetof.

    – Brian
    7 hours ago











  • Doesn't that violate the strict-aliasing rule? Or is that a C-only rule?

    – sturcotte06
    7 hours ago







  • 1





    @sturcotte06 it does not because of If two objects are pointer-interconvertible, then they have the same address, and it is possible to obtain a pointer to one from a pointer to the other via a reinterpret_­cast.

    – NathanOliver
    7 hours ago







1




1





Thanks, I knew that I left a hole in my question. So, if I used something(&p.y); return p.x;, then it is clearly a missed optimization?

– geza
8 hours ago





Thanks, I knew that I left a hole in my question. So, if I used something(&p.y); return p.x;, then it is clearly a missed optimization?

– geza
8 hours ago













@geza For some definition of "clearly". There almost certainly exists a lot of code that does things like this that such an optimization would break.

– Barry
7 hours ago





@geza For some definition of "clearly". There almost certainly exists a lot of code that does things like this that such an optimization would break.

– Barry
7 hours ago




1




1





@geza Technically, yes, it would be a missed optimization then, but I don't think major compilers, at this time, are prepared to break all the existing code that uses offsetof.

– Brian
7 hours ago





@geza Technically, yes, it would be a missed optimization then, but I don't think major compilers, at this time, are prepared to break all the existing code that uses offsetof.

– Brian
7 hours ago













Doesn't that violate the strict-aliasing rule? Or is that a C-only rule?

– sturcotte06
7 hours ago






Doesn't that violate the strict-aliasing rule? Or is that a C-only rule?

– sturcotte06
7 hours ago





1




1





@sturcotte06 it does not because of If two objects are pointer-interconvertible, then they have the same address, and it is possible to obtain a pointer to one from a pointer to the other via a reinterpret_­cast.

– NathanOliver
7 hours ago





@sturcotte06 it does not because of If two objects are pointer-interconvertible, then they have the same address, and it is possible to obtain a pointer to one from a pointer to the other via a reinterpret_­cast.

– NathanOliver
7 hours ago













-4
















Given a POD structure (trivial with a standard layout, such as Point), you could change y as follows, even if x was not the first field in the object:



void something(int *data)

 data[(offsetof(Point, y)- offsetof(Point, x))/sizeof(int)] = 3;






share|improve this answer



























  • You might want to reread the question. The OP is not asking about this.

    – NathanOliver
    7 hours ago











  • The OP says Is there something in the standard, which allows something to modify p.y, if we only give access to p.x?

    – Gonen I
    7 hours ago











  • Correct. You are talking about an array, not whether or not something could modify y given a pointer to x.

    – NathanOliver
    7 hours ago











  • The result will be the same. It is not possible for the compiler to optimize, as the data is freely changeable by something given its prototype.

    – Gonen I
    7 hours ago











  • Sure, but arrays are different than structs and you cannot treat a pointer to a member as a pointer to an array. You also don't back up you claim with any text from the standard.

    – NathanOliver
    7 hours ago















-4
















Given a POD structure (trivial with a standard layout, such as Point), you could change y as follows, even if x was not the first field in the object:



void something(int *data)

 data[(offsetof(Point, y)- offsetof(Point, x))/sizeof(int)] = 3;






share|improve this answer



























  • You might want to reread the question. The OP is not asking about this.

    – NathanOliver
    7 hours ago











  • The OP says Is there something in the standard, which allows something to modify p.y, if we only give access to p.x?

    – Gonen I
    7 hours ago











  • Correct. You are talking about an array, not whether or not something could modify y given a pointer to x.

    – NathanOliver
    7 hours ago











  • The result will be the same. It is not possible for the compiler to optimize, as the data is freely changeable by something given its prototype.

    – Gonen I
    7 hours ago











  • Sure, but arrays are different than structs and you cannot treat a pointer to a member as a pointer to an array. You also don't back up you claim with any text from the standard.

    – NathanOliver
    7 hours ago













-4














-4










-4









Given a POD structure (trivial with a standard layout, such as Point), you could change y as follows, even if x was not the first field in the object:



void something(int *data)

 data[(offsetof(Point, y)- offsetof(Point, x))/sizeof(int)] = 3;






share|improve this answer















Given a POD structure (trivial with a standard layout, such as Point), you could change y as follows, even if x was not the first field in the object:



void something(int *data)

 data[(offsetof(Point, y)- offsetof(Point, x))/sizeof(int)] = 3;







share|improve this answer














share|improve this answer



share|improve this answer








edited 6 hours ago

























answered 7 hours ago









Gonen IGonen I

2,07714 silver badges31 bronze badges




2,07714 silver badges31 bronze badges















  • You might want to reread the question. The OP is not asking about this.

    – NathanOliver
    7 hours ago











  • The OP says Is there something in the standard, which allows something to modify p.y, if we only give access to p.x?

    – Gonen I
    7 hours ago











  • Correct. You are talking about an array, not whether or not something could modify y given a pointer to x.

    – NathanOliver
    7 hours ago











  • The result will be the same. It is not possible for the compiler to optimize, as the data is freely changeable by something given its prototype.

    – Gonen I
    7 hours ago











  • Sure, but arrays are different than structs and you cannot treat a pointer to a member as a pointer to an array. You also don't back up you claim with any text from the standard.

    – NathanOliver
    7 hours ago

















  • You might want to reread the question. The OP is not asking about this.

    – NathanOliver
    7 hours ago











  • The OP says Is there something in the standard, which allows something to modify p.y, if we only give access to p.x?

    – Gonen I
    7 hours ago











  • Correct. You are talking about an array, not whether or not something could modify y given a pointer to x.

    – NathanOliver
    7 hours ago











  • The result will be the same. It is not possible for the compiler to optimize, as the data is freely changeable by something given its prototype.

    – Gonen I
    7 hours ago











  • Sure, but arrays are different than structs and you cannot treat a pointer to a member as a pointer to an array. You also don't back up you claim with any text from the standard.

    – NathanOliver
    7 hours ago
















You might want to reread the question. The OP is not asking about this.

– NathanOliver
7 hours ago





You might want to reread the question. The OP is not asking about this.

– NathanOliver
7 hours ago













The OP says Is there something in the standard, which allows something to modify p.y, if we only give access to p.x?

– Gonen I
7 hours ago





The OP says Is there something in the standard, which allows something to modify p.y, if we only give access to p.x?

– Gonen I
7 hours ago













Correct. You are talking about an array, not whether or not something could modify y given a pointer to x.

– NathanOliver
7 hours ago





Correct. You are talking about an array, not whether or not something could modify y given a pointer to x.

– NathanOliver
7 hours ago













The result will be the same. It is not possible for the compiler to optimize, as the data is freely changeable by something given its prototype.

– Gonen I
7 hours ago





The result will be the same. It is not possible for the compiler to optimize, as the data is freely changeable by something given its prototype.

– Gonen I
7 hours ago













Sure, but arrays are different than structs and you cannot treat a pointer to a member as a pointer to an array. You also don't back up you claim with any text from the standard.

– NathanOliver
7 hours ago





Sure, but arrays are different than structs and you cannot treat a pointer to a member as a pointer to an array. You also don't back up you claim with any text from the standard.

– NathanOliver
7 hours ago


















draft saved

draft discarded















































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.




draft saved


draft discarded














StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f57979009%2fis-it-possible-to-get-a-pointer-to-one-subobject-via-a-pointer-to-a-different-u%23new-answer', 'question_page');

);

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







-

Popular posts from this blog

Canceling a color specificationRandomly assigning color to Graphics3D objects?Default color for Filling in Mathematica 9Coloring specific elements of sets with a prime modified order in an array plotHow to pick a color differing significantly from the colors already in a given color list?Detection of the text colorColor numbers based on their valueCan color schemes for use with ColorData include opacity specification?My dynamic color schemes

Image
Would it be easier to colonise a living world or a dead world? Postal services in Italy - Poste Italiane vs. Friendpost vs. GPS What is /dev/null and why can't I use hx on it? Why are engines with carburetors hard to start in cold weather? How to make a gift without seeming creepy? Without exposing his identity, did Roy help his parents with money so that they can afford to stay in their home? Does the Creighton Method of Natural Family Planning have a failure rate of 3.2% or less? How do I break the broom in Untitled Goose Game? Had there been instances of national states banning harmful imports before the mid-19th C Opium Wars? D&D Monsters and Copyright Is sleeping on the groud in cold weather better than on an air mattress? Transiting through Switzerland by coach with lots of cash quadratic equations on 2 by 2 matrices Always Lubricate Skewers? I pay for a service, but I miss the broadcast Iron-age tools, is there a way to extract heavy metals ...
Read more

Invision Community Contents History See also References External links Navigation menuProprietaryinvisioncommunity.comIPS Community ForumsIPS Community Forumsthis blog entry"License Changes, IP.Board 3.4, and the Future""Interview -- Matt Mecham of Ibforums""CEO Invision Power Board, Matt Mecham Is a Liar, Thief!"IPB License Explanation 1.3, 1.3.1, 2.0, and 2.1ArchivedSecurity Fixes, Updates And Enhancements For IPB 1.3.1Archived"New Demo Accounts - Invision Power Services"the original"New Default Skin"the original"Invision Power Board 3.0.0 and Applications Released"the original"Archived copy"the original"Perpetual licenses being done away with""Release Notes - Invision Power Services""Introducing: IPS Community Suite 4!"Invision Community Release Notes

Image
Internet forum softwarePHP software Internet communityPHPMySQLdatabase management systemInternet forumCharles WarnerMatt MechamJarvis Entertainment GroupIkonboardInvisionFreeAjaxIPS Community ForumsIPS Community Forumsthis blog entry Invision Community From Wikipedia, the free encyclopedia Jump to navigation Jump to search Invision Community Developer(s) Invision Power Services Stable release 4.4.6 / August 19, 2019 ; 34 days ago  ( 2019-08-19 ) Platform PHP / MySQL Type Forum software License Proprietary Website invisioncommunity.com Invision Community (previously known as IPS Community Suite ) is primarily an Internet community software produced by Invision Power Services, Inc. It is written in PHP and uses MySQL as a database management system. Invision Power Services sell applications that each can be bought and installed separately in addition to the Suite, the most widely known being the Internet forum software Invision Power Boar...
Read more

199年 目錄 大件事 到箇年出世嗰人 到箇年死嗰人 節慶、風俗習慣 導覽選單

Image
199年 平年 199年 出自維基百科 跳至導覽 跳至搜尋 世紀： 1世紀 2世紀 3世紀 年代： 160年代 170年代 180年代 190年代 200年代 210年代 220年代 年： 194年 195年 196年 197年 198年 199年 200年 201年 202年 203年 204年 干支年： 己卯年 （ 兔年 ） 年號： 199年 係平年。 目錄 1 大件事 2 到箇年出世嗰人 3 到箇年死嗰人 4 節慶、風俗習慣 大件事 199...
Read more