Question: I have a really simple example which I've written on [JSBin](http://jsbin.com/iwihox/1/edit). It looks like this:

![a](https://i.imgur.com/8Fwii1J.png)

All I'd like to do is simply take two divs of a given width and height and display them side-by-side without a gap between them. I've used `display: inline-block` to accomplish the above, but it seems like it refuses to chomp the whitespace between divs, which seems to completely violate the idea of the separation of content and styling.

Here's my HTML:

```
<div class="container">
  <div class="a">
    <!-- completely empty -->
  </div>

  <div class="b">
    <!-- nothing at all -->
  </div>
</div>

```

and here's my CSS:

```
.container {
  display: inline-block;
}

.a {
  width: 320px;
  height: 240px;

  display: inline-block;

  background-color: #83C5D1;
}

.b {
  width: 180px;
  height: 240px;

  display: inline-block;

  background-color: #B2D9D6;
}

```

How can I work around this to get them snug together without touching my HTML?

Answer: 
The disassembler (IDA Demo, specifically) misled me by uniting several commands into one line. It made a single `mov` line out of a `mov-orr-orr` sequence that was meant to assign a full 32-bit constant to a register. The thunks were Thumb after all. The linker works as designed.

IDA is otherwise great. I knew in the back of my mind about this particular behavior regarding ARM, but this time it slipped.

My bad, thanks and upvotes to everyone who tried to help.
You might be well have a valid / real problem on your hand. Afaik Windows Phone environment is [required to be Thumb-2 only](http://msdn.microsoft.com/en-us/library/jj919377.aspx), so linker you are using might not be able to handle calls to ARM mode. See the same link for some considerations when you are mixing assembly and C.

If this was a Linux / ELF question, I would have answered differently;

> 
> 
> > 
> > The address under pFunc is generated by the linker, since it's a cross-module call. So the low bit is placed there by the linker.
> > 
> > 
> > 
> 
> 
> 

`pFunc` is generated by `compiler` and a `linker` will fix it when you are building a loadable image which will already be fully resolved for static relocation of calls. All portable object files should contain a table about function modes so later linkers can process them and do relocation and updating call sequences accordingly.

See [ELF for the ARM Architecture - 4.6 Relocation](http://infocenter.arm.com/help/topic/com.arm.doc.ihi0044e/IHI0044E_aaelf.pdf) for how this is done via `ELF` files.