I am working in 8 to 8 work days, and even goes back to work during my weekends. I do not receive overtime or any other benefits.
You are a programmer. In the US, by Federal statute, we programmers are "exempt" which means that in the absense of a union contract to the contrary, we don't get overtime.
29 U.S.C. § 213 a(17) any employee who is a computer systems analyst, computer programmer, software engineer, or other similarly skilled worker
Is this a norm in software projects?
You are describing a death march, which is the norm in software development. I usually recommend reading the book Death March. This book should give you ideas of what sort of death marches might appeal to you, and which you should walk away from. It is an occupational hazard and the reason that many developers quit before they hit 35ish. Staying at the office for 12 hour days is hard, and becomes impossible when you have a wife who wonders if you are cheating on her, or children you never see. Listen to the lyrics of the song Cat's Cradle.
Not all companies do this, some just have no clue what they are doing and this is the sort of mess that comes out of managers. And some companies plan on losing staff to burnout and plan it into budgets and schedules. Perhaps you ought to read the rant by EA_Spouse about this sort of thing.
My recommendation for death marches is to get lots of sleep and exercise. When you go home, "forget" your pager and cellphone about half the time. If they are paying for the cell phone, leave it at the office every night.
edit: there was insufficient room to answer Rein's comment in the comment section, so I'm adding more details here.
From the preface of Death March:
industry surveys ... as well as statistical data ... suggest that the average project is likely to be 6 to 12 months behind schedule and 50 to 100 percent over budget.
So the real questions are: If you can't avoid death march projects, how can you survive them? What should you do to increase your chances of success? When should you be willing to compromise—and when should you be willing to put your job on the line and resign if you can't get your way? That is what this book is about.
I can't tell you if you will or will not like Death Marches. Some death marches can and do appeal to the participants, and those score high on the "happiness" scale. The ones Yourdon labeled "kamikaze" might be ones that normally you'd describe as "glorious failures" but you'll never work with such amazing people/technology/whatever again, so going down with the ship is not necessarily undesirable. "Mission Impossible" style death marches are the sort of things where you know that if your competitor gets X to the market ahead of you, then they'll steal your oxygen and your company will shrivel up and die.
What makes you happy isn't necessarily what makes me happy, and juniordeveloper87 needs to understand that what he's (or she, but most likely "he" from the demographics of our profession) experiencing right now is not unusual, not uncommon and more likely than not to happen over and over again. I constantly recommend reading the book Death March because it will help the reader understand what goes on, what will go on and how to cope with it. Sometimes the way to cope is to quit. Sometimes to just suck it up and go on. You, me, everyone has to learn that for ourselves; and we need to learn what our own limits are.
I've worked on projects in all 4 quadrants, and the ones high on happiness are bearable and sometimes a lot of fun. It is my experience that "ugly" death marches are the most common of all.
As appalling as the advice "just get used to it" sounds, it is the only rational advice for practitioners in this field. If you are unwilling and unable to "get used to it" then you are going to need to find another career, or join a union. Otherwise you will burn out. There are too many idiots running companies and countries to get away from the stupidity. We do not live in a meritocracy. We live in a world run by the people who used to (and some still do) beat up nerds, and the majority of us were, are and will be nerds.