you are making this way, way too hard. Do not use a goto unless you can't do the same thing with a loop or another tool. There are not many reasons to use goto in c++.
this looks like what happens when you code before thinking and designing the answer.
can you say, in words not code, exactly how you plan to solve this problem? If you cannot, then you sure can't code it!
first, you may not have an answer, so how will you handle that? The numbers are random or user input, either way, if the values are 3,5,7,9, what is the max and min even values? There are none, and you should say this. Same for odd, if all the numbers were even.
what happens if you do things as you get them?
in pseudo code.. consider:
b = rand...
... lots of logic for each one after a.
if(a and b are both even or odd and a > b) a is max{even or odd} and b is min{even or odd}
if(a and b are both even or odd and a < b){set a = min{e/o} b = max{e/o}
--update ihazeven/ihazodd if not both same as well
and c is the same except compare to both a and b,
and n is the same except even more compares, to a,b,c
however for c and n you already know how a relates to b, so if c is >a, and a > b, you know something, you don't need to check c > b, you know this.