Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 8564011
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 11, 20262026-06-11T17:06:02+00:00 2026-06-11T17:06:02+00:00

I understand why memory barriers are needed, but I don’t get it in the

  • 0

I understand why memory barriers are needed, but I don’t get it in the case of Uniprocessor.

Do I have to deal with barriers even when I use UP? Every document explains them with SMP but not UP.

In the following code, is there any possibility that r2 == 0 in point a?

// the location 0xdeadbeef has a zero initial value
ldr r0, =0xdeadbeef
ldr r1, =0xdeadbeef
ldr r2, =1
str r2, [r0]
ldr r2, [r1]
// point a
  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-06-11T17:06:03+00:00Added an answer on June 11, 2026 at 5:06 pm

    There are memory barriers and compiler barriers.

    Memory barriers are not required on a single processor (I’m not sure if hyperthreading counts as multiple processors) but compiler barriers are – the compiler could re-order the code in different threads such that you fail.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I'm starting to understand memory management better in objective-c, but there's something I don't
I have a simple example of what I don't understand about memory management on
There's something I don't understand about memory barrier use and I'm hoping for clarification.
I am trying to understand how memory management goes on low level and have
I understand Objective-C memory management but I'm using Core Graphics functionality such as CGRect,
I cannot understand the Java memory usage. I have an application which is executed
I understand that in CUDA's memory hierachy, we have things like shared memory, texture
I think I understand memory alignment, but what confuses me is that the address
I have been trying to understand segmented memory and I came across this statement
From what I have read, and the way I understand how memory structures work,

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.